Skip to main content
Glama

Save model handoff

ricursor_handoff

Save structured task IDs and versioned rule decisions; never include prompts or 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>",
      "task_id": "<task_id>",
      "expected_version": "<expected_version>",
      "state": "<state>"
    },
    "name": "ricursor_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
projectYesProject name inside the workspace.
task_idYes
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations supply only openWorldHint=false, so the description carries the full burden for a write operation and does not say whether this creates or overwrites, what happens when expected_version is stale, or whether a version conflict surfaces as an error. The one genuine behavioral disclosure — the prohibition on including prompts or source text — is useful and specific, but it is the only one.

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 no filler; the sensitive-data prohibition is placed where it will be read. It is efficient, though the terseness borders on under-specification for a four-parameter nested-object tool.

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 mutation tool with a nested required state object, a concurrency parameter, no output schema, and minimal annotations, the description covers only a fraction of what an agent needs. It never explains the version-conflict contract or the accepted/conflict status enum nested in decisions, both of which materially affect correct invocation.

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 25% across four required parameters including a nested state object, so the description must compensate. It gestures at task_id and state.decisions ('task IDs', 'versioned rule decisions') but says nothing about expected_version semantics, project scope, or the completed/pending arrays, leaving the most consequential parameter (the version guard) unexplained.

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+resource pair: 'Save structured task IDs and versioned rule decisions.' An agent can tell this persists handoff state rather than checking, consuming, or reporting like the sibling tools. It stops short of naming any sibling to steer away from, so it is clear but not fully differentiated.

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 alternatives such as ricursor_snapshot or ricursor_ledger that might also persist state. The only directive ('never include prompts or source') is a content restriction, not usage routing.

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