Skip to main content
Glama

analyze

Answer why, when, which-commit, or impact questions about a repository with cited file:line and commit evidence, plus leads to verify.

Instructions

Start here for a why, when, which-commit or what-does-it-affect question: a verdict, answer claims and leads with file:line and commit hashes. Leads are what to read next, not claims; confirm one with your own git or grep. needs_clarification is normal: ask the user.

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

Input Schema

NameRequiredDescriptionDefault
showNo'lead': also the first lead's numbered source lines (at most 60).
questionYesThe question.
budget_secondsNoWall-time budget in seconds (1-600).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / show
      Added value: +{
      +  "anyOf": [
      +    {
      +      "const": "lead",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "'lead': also the first lead's numbered source lines (at most 60)."
      +}
  2. Changed7 schema fields changedv0.4.0
    • removedInput schema / properties / budget_calls
      Removed value: -{
      -  "default": 40,
      -  "description": "Internal tool-call budget (1-200).",
      -  "type": "integer"
      -}
    • removedInput schema / properties / observe
      Removed value: -{
      -  "default": false,
      -  "description": "Trace the tests that reach the answer with the runtime call tracer (isolated copy) and attach what they observed.",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / plan_json
      Removed value: -{
      -  "default": "",
      -  "description": "A checked question plan as JSON text (from `verinoda plan check`); used instead of drafting one.",
      -  "type": "string"
      -}
    • removedInput schema / properties / question / default
      Removed value: -""
    • changedInput schema / properties / question / description
      Previous value: -"The question to answer with claims and evidence (optional when plan_json is given: the plan's user_message is used)."New value: +"The question."
    • removedInput schema / properties / run_tests
      Removed value: -{
      -  "default": false,
      -  "description": "Also run the tests that statically reach the answer (isolated copy, allowlisted runners only).",
      -  "type": "boolean"
      -}
    • addedInput schema / required
      Added value: +[
      +  "question"
      +]
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, it discloses the output shape (verdict, answer claims, leads with file:line and commit hashes), clarifies that leads are not claims, and normalizes needing clarification from the user. It does not address the readOnlyHint=false annotation or explain whether any side effects are possible, but it adds useful behavioral context.

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

Conciseness5/5

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

The description is front-loaded with 'Start here' and uses only three short sentences, each carrying distinct information: entry-point guidance, lead semantics, and clarification behavior. There is no redundant or filler text.

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

Completeness4/5

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

For an analysis tool with no output schema, the description sufficiently explains the return format and how to treat leads and clarification responses. It leaves budget_seconds behavior to the schema, which is acceptable given full schema coverage.

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?

Schema description coverage is 100%, so the schema already defines question, show, and budget_seconds. The description implies the question parameter through its list of question types but does not add semantic detail for show or budget_seconds, so baseline 3 is appropriate.

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 clearly states the tool answers why/when/which-commit/what-does-it-affect questions and returns a verdict with claims and leads. This is much more specific than the generic name 'analyze', though it does not explicitly name or contrast sibling tools.

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 a strong entry-point cue with 'Start here' for the listed question types, and explains that leads must be confirmed with the user's own git or grep. It does not explicitly state when not to use the tool or name alternative sibling tools for other question types.

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