Skip to main content
Glama

Sync repository

ricursor_snapshot

Sync locally extracted JS/TS structural metadata only; never transmit source.

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>",
      "files": "<files>"
    },
    "name": "ricursor_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes
projectYesProject name inside the workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

The only annotation is openWorldHint=false, so the description carries nearly the full behavioral burden. It does add one genuinely useful guarantee beyond the annotations: only structural metadata is transmitted and source is never sent, which is exactly the kind of data-handling fact an agent cannot get from structured fields. It says nothing about expected_version conflict handling, the 20-file batch cap, or what happens on partial failure.

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 single clause is front-loaded and free of filler, but for a tool taking a nested array of up to 20 file records with a version field, that brevity reads as under-specification rather than discipline. Nothing is wasted, yet the sentence is not sized to the tool's complexity.

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?

With no output schema, minimal annotations, and a nested input containing required hash/metadata/expected_version subfields, the definition leaves an agent unable to determine conflict semantics, batch limits, or what a successful sync returns. The privacy guarantee is welcome but does not fill those gaps.

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 50%: 'project' is documented in the schema, while the entire 'files' array, its nested path/hash/metadata shape, and the optimistic-concurrency 'expected_version' field are undocumented. The description says nothing about any parameter and does not compensate for the coverage gap.

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 names a specific action (sync) and a specific resource (locally extracted JS/TS structural metadata), which is far more informative than the bare name 'ricursor_snapshot'. It does not, however, distinguish this tool from any sibling such as ricursor_check or ricursor_handoff, so an agent must infer that this is the write/upload path.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative in the twelve-sibling catalog. The agent is told what the tool does but not the conditions under which it should be selected over ricursor_check or ricursor_ledger.

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