Skip to main content
Glama

build

Idempotent

Generate or refresh the repository code graph to reveal symbol usage, change impact, and architecture; run it before analysis and after large edits, optionally reparsing all files.

Instructions

Build or refresh the code graph of the repository (incremental; full=true reparses every file); call it first and after large edits.

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": "build"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoReparse every file instead of only changed ones.
exclude_dirsNoDirectory names to skip, e.g. ["generated"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the build is incremental by default and full=true reparses every file, which signals a cost/effort tradeoff. It does not say whether the graph is persisted or returned, or whether concurrent builds are safe.

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?

One sentence, front-loaded with the core action, with a parenthetical that qualifies cost and a trailing clause that covers timing. Nothing is wasted and nothing important is buried.

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 a two-parameter, zero-required-parameter tool with full schema coverage and full annotation coverage, the description covers purpose, mode semantics and invocation timing. The only real gap is the absence of any statement about the result of the build (persisted state vs. returned value), which matters since there is no output schema.

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 coverage is 100%, so both parameters are already documented, including defaults. The description reinforces the incremental-vs-full distinction but adds no syntax or edge-case detail beyond the schema; exclude_dirs is left entirely to the schema, so the baseline 3 applies.

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?

States a specific verb and resource: 'Build or refresh the code graph of the repository', with the scope (repository-wide) made explicit. It implicitly distinguishes itself from the query-oriented siblings by being the graph-construction step, though it never names an alternative to contrast with.

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?

'call it first and after large edits' gives concrete timing guidance, including the prerequisite role relative to the sibling query/analysis tools. It lacks an explicit when-not condition (e.g. small single-file edits) or a named alternative, which keeps it below a 5.

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