Skip to main content
Glama

Check tree

code_check
Read-only

Every problem in a tree, now or as of a change: files that do not parse, imports and page references to nothing, names a file does not export, packages not pinned.

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": {
      "tree": "<tree>",
      "org": "<org>"
    },
    "name": "code_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose trees and sites to use. Required on every call, even when only one organization is listed; a path never names it.
treeYesThe tree's name.
changeIdNoCheck the tree as of this change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description usefully scopes what counts as a "problem" and notes the historical snapshot mode. It omits cost/latency expectations for a whole-tree lint and says nothing about result shape or whether findings block anything.

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 a compact colon-led enumeration; every clause names a distinct check. It is terse to the point of being elliptical in places ("names a file does not export"), but nothing is wasted.

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?

With no output schema, the description carries the burden of describing results, and the category list effectively tells the agent what findings look like. Combined with the annotations, an agent has enough to call it correctly; only latency/cost expectations for a full-tree check are absent.

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% and each parameter is already documented, including changeId as "Check the tree as of this change." The description's "now or as of a change" restates that same distinction rather than adding format, defaults, or constraints beyond the schema. 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?

The description states a specific resource and outcome — problems in a tree, enumerated by category (unparsable files, dangling imports/page refs, missing exports, unpinned packages). An agent can tell this is a lint/consistency check rather than a read or edit. It stops short of explicitly distinguishing itself from the wiki counterpart (wiki_check).

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?

"now or as of a change" implies when changeId should be supplied versus omitted, which is useful. However, there is no explicit when-to-use, no exclusions, and no pointer to alternatives such as wiki_check for wiki content; the routing has to be inferred from the word "tree".

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