understand_physical_problem — SkoIA Parts MCP Tool
understand_physical_problem
(understand physical problem) is one of 15 tools on the
SkoIA Parts
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call understand_physical_problem from your client
- Claude Code SkoIA Parts understand_physical_problem run in your project directory
- Claude Desktop SkoIA Parts understand_physical_problem ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SkoIA Parts understand_physical_problem ~/.cursor/mcp.json
- VS Code SkoIA Parts understand_physical_problem .vscode/mcp.json
- Zed SkoIA Parts understand_physical_problem ~/.config/zed/settings.json
- Windsurf SkoIA Parts understand_physical_problem ~/.codeium/windsurf/mcp_config.json
- Cline SkoIA Parts understand_physical_problem ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SkoIA Parts understand_physical_problem ~/.gemini/settings.json
- Grok SkoIA Parts understand_physical_problem .mcp.json (in your project root)
- ChatGPT SkoIA Parts understand_physical_problem Settings → Connectors → Advanced → Developer mode
- Claude.ai SkoIA Parts understand_physical_problem Settings → Connectors → Add custom connector
- LangChain SkoIA Parts understand_physical_problem pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http skoia-parts https://parts.skoia.me/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.