Skip to main content
Glama

Troubleshoot a connection

troubleshoot
Read-onlyIdempotent

Sourced fixes for errors when connecting Apify Actors to Claude, Cursor, VS Code, ChatGPT, Codex, Gemini CLI or n8n (401 unauthorized, 408 timeouts, 429, SSE endpoint gone, tools missing, result too large...).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "problem": "<problem>"
    },
    "name": "troubleshoot"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
clientNoOptional: the client, e.g. 'Cursor'.
problemYesThe error message or symptom.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered elsewhere. The description adds one genuinely new behavioral fact — the fixes are 'sourced', implying cited/authoritative returns — but says nothing about how results are retrieved, how many are returned, or what happens when no matching fix exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the core value ('sourced fixes') first and the scope details in a compact parenthetical. The error and client lists are long but each item carries routing value; only mild cost is the trailing ellipsis, which leaves the covered error set open-ended.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter read-only lookup with one required field and no output schema, the description covers the domain well. What is missing is the outcome contract — whether 'sourced fixes' means a list of step-by-step remediations, links, or recipes — and what happens on a no-match, which an agent may need to decide whether to escalate to another tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 67% schema coverage, the schema already documents 'problem' (error message or symptom) and 'client'. The description usefully enumerates supported clients (Cursor, VS Code, ChatGPT, Codex, Gemini CLI, n8n) and problem categories, which enriches the 'client' and 'problem' arguments beyond the schema. The 'limit' parameter (1-6, default 3) is never explained, so the description does not fully compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the concrete deliverable ('Sourced fixes for errors when connecting Apify Actors to...') and enumerates the exact symptom classes it covers (401, 408, 429, SSE endpoint gone, tools missing, result too large). An agent can tell instantly that this is a troubleshooting/knowledge-lookup tool, not a config builder or tool search, which separates it from every listed sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the error taxonomy: an agent knows to call this when it hits a connection error with one of the named clients. However, the description never states when NOT to use it or points to an alternative (e.g., build_mcp_config for setup problems, find_recipe for workflow issues), so the routing decision is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources