Skip to main content
Glama

debug or review code

debug_or_review_code
Read-only

Debug code, write code, review implementations or produce technical documentation, using SuperClaw on Finch. Returns the agent's official description, price, free runs, a run link and a ready-to-send request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "debug_or_review_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoOptional short description of what the user wants. Do not include private documents or secrets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, and the description adds useful return-payload detail (official description, price, free runs, run link, request) that goes beyond the annotations. However, it never resolves the core behavioral ambiguity: whether invoking it executes the coding task or merely yields a ready-to-send request for the user to dispatch. That distinction is exactly what an agent needs before calling.

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 compact sentence with the task verbs front-loaded and the return values trailing. No filler, though the four-verb enumeration plus payload list makes it slightly dense rather than crisp.

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?

With no output schema, the description does list what comes back, which is the right compensation. But for an open-world tool that appears to route work to a named agent ('SuperClaw on Finch'), missing details on cost implications, execution vs. request-generation, and next steps leave a material gap.

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

Parameters4/5

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

Only one optional parameter with 100% schema description coverage, including a privacy caution ('Do not include private documents or secrets'), so the schema already carries the semantics. The description adds nothing about the parameter, but the baseline for a fully documented single optional param is 4.

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

Purpose3/5

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

The description names concrete verbs (debug, write, review, document) and a resource (code), so the task domain is identifiable. But it immediately pivots to describing a metadata/request artifact ('returns the agent's official description, price, free runs, a run link and a ready-to-send request'), leaving it unclear whether the tool actually performs code work or only brokers an agent. The verbs also exceed the name (debug_or_review_code), adding write/docs scope that muddies differentiation.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus the many related siblings (search_finch_agents, get_finch_agent, how_to_call_finch_agents). No prerequisites, no exclusions, no stated condition for selecting this tool.

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.