Skip to main content
Glama

Check planned write

ricursor_check
Read-only

Stop on block or errors. Checks tracked versions, exports and accepted import boundaries; never writes code.

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": {
      "project": "<project>",
      "path": "<path>",
      "hash": "<hash>",
      "metadata": "<metadata>",
      "expected_version": "<expected_version>",
      "dependencies": "<dependencies>"
    },
    "name": "ricursor_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYes
pathYes
projectYesProject name inside the workspace.
metadataYes
dependenciesYes
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so 'never writes code' mostly restates structured data. The one genuine addition is the instruction to halt on block or error outcomes, but it never explains what a 'block' is, what conditions produce one, or what the response contains.

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?

Two short sentences with no filler, but the front-loaded 'Stop on block or errors' is the least informative part and reads as a fragment, while the substantive scope statement is buried in the second clause.

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 six-parameter, all-required tool with nested objects, no output schema, and near-zero schema descriptions, the definition should carry much more weight. An agent cannot tell what hash or dependencies must contain, or how to interpret a block versus an error result.

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

Parameters2/5

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

Schema description coverage is only 17% (just 'project'), and six required parameters include nested metadata, dependencies, hash, path and expected_version. The description gestures at expected_version ('tracked versions'), metadata.exports and metadata.imports, but leaves hash, path, and dependencies entirely unexplained in both schema and description.

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 the resources checked (tracked versions, exports, import boundaries) and states it never writes code, which gives a rough sense of a pre-write validation step. But 'ricursor_check' is not distinguished from siblings such as ricursor_action_check or ricursor_action_group_check, and the opening phrase 'Stop on block or errors' obscures rather than clarifies the verb+resource.

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?

'Stop on block or errors' is a directive about reacting to results, not guidance on when to call this tool versus the action_check siblings. There is no statement of prerequisites (e.g., call before a planned write) or exclusions.

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