Skip to main content
Glama

run_tool

Runs one selected Verinoda analysis—locating text, inspecting symbols, tracing call paths, reviewing edits, or querying claims—to answer repository questions with verifiable source evidence.

Instructions

Run one more Verinoda tool: locate {text}, coupled {files}: files an issue touches, files that change together; node_inspect {name}: a symbol's definition and edges; relation_trace {source, target}: call paths between symbols; map_view {view, targets?}: architecture views (impact, hierarchy, ...); claim_list {status?}, claim_inspect {claim_id}, evidence_inspect {evidence_id}: claims, evidence; change_review {targets?, change?, since_last?}: what an edit touches; history_search {text|symbol|message|base}: when text came or went, commits; tq {questions}: typed questions, many per call.

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": {
      "name": "<name>"
    },
    "name": "run_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe tool.
argumentsNoIts arguments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • changedInput schema / properties / arguments / description
      Previous value: -"Its arguments, e.g. {\"name\": \"Cls.method\"}."New value: +"Its arguments."
    • changedInput schema / properties / name / enum
      Previous value: -[
      -  "node_inspect",
      -  "relation_trace",
      -  "map_view",
      -  "claim_inspect",
      -  "claim_list",
      -  "evidence_inspect",
      -  "change_review",
      -  "history_search",
      -  "grep_context",
      -  "read_context"
      -]New value: +[
      +  "locate",
      +  "coupled",
      +  "node_inspect",
      +  "relation_trace",
      +  "map_view",
      +  "claim_inspect",
      +  "claim_list",
      +  "evidence_inspect",
      +  "change_review",
      +  "history_search",
      +  "tq",
      +  "grep_context",
      +  "read_context"
      +]
  2. Addedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is partly covered, but the description does not say which sub-tools read versus write or what side effects occur. 'One more' implies a single dispatch per call, which is useful behavioral context. Return shape, error behavior, and permission needs are absent.

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

Conciseness3/5

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

The content is dense but relevant, with little wasted text. However, it is a single semicolon-delimited run-on with no clear grouping or front-loading of sub-tools by category. Structure could be much better for a 13-value dispatcher.

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

Completeness2/5

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

For a dispatcher with 13 enum values and no output schema, the description leaves two sub-tools (grep_context, read_context) entirely undocumented. It also provides no return-value or error guidance. That is a clear completeness gap for a tool whose whole job is selecting and parameterizing sub-tools.

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?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the enum by attaching argument signatures to most sub-tools (locate needs text, relation_trace needs source and target, tq needs questions), which meaningfully clarifies the opaque 'arguments' object. It omits grep_context and read_context, both present in the enum.

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

Purpose4/5

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

The description opens with a specific verb and resource: it runs one Verinoda tool and enumerates the selectable sub-tools. That is far more concrete than the generic name 'run_tool'. It does not differentiate from siblings like project_query or analyze, so it stops short of a 5.

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

Usage Guidelines4/5

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

It gives implicit routing guidance by pairing each sub-tool with its key arguments (e.g., locate {text}, relation_trace {source, target}, tq {questions}). That helps an agent choose the right enum value. It never says when to use this tool instead of project_query/analyze/code_check, and there are no exclusions.

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

Deploy Server

Other Tools