Skip to main content
Glama

Propose action

ricursor_action_check

Metadata-only decision for a JS/TS write or delete. Returns allow or block (with reasons to fix) plus a one-use receipt. Never send 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": {
      "kind": "<kind>",
      "project": "<project>",
      "action_id": "<action_id>",
      "path": "<path>",
      "baseline_hash": "<baseline_hash>"
    },
    "name": "ricursor_action_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
pathYes
projectYes
metadataNo
action_idYesUnique per proposed action, 8-80 characters.
result_hashNo
dependenciesNo
baseline_hashYes
expected_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations provide only openWorldHint=false, so the description carries most of the burden. It discloses solid behavior: metadata-only input, allow/block output with remediation reasons, and issuance of a one-use receipt (i.e. the call has a side effect despite being a 'check'). It does not say whether the receipt expires, whether repeated calls are idempotent, or what happens after a block beyond 'reasons to fix'.

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?

Three short sentences, front-loaded with the operation and output, then the critical security constraint. Every sentence carries information and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description usefully substitutes for the missing output schema by describing the allow/block result and receipt. But for a 9-parameter, nested-object tool with near-zero schema documentation, the request-building semantics (hashes, version, dependencies) remain unexplained, so an agent cannot confidently construct a correct call from the definition alone.

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 11% — only action_id is documented — across 9 parameters including nested dependencies and three hash/version fields. The description only indirectly clarifies one thing: 'metadata-only' and 'Never send source' tell the agent that metadata must exclude source code. Nothing explains baseline_hash, result_hash, expected_version, or dependencies, which are exactly the fields an agent is most likely to misuse.

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 operation: a metadata-only decision gate for a JS/TS write or delete that returns allow/block and a one-use receipt. That is far more than a restatement of the name, and it distinguishes the tool's job from a general 'check'. It does not, however, differentiate itself from the visible siblings ricursor_check or ricursor_action_group_check, so the agent must infer the boundary.

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?

Usage is only implied: you call this before performing a write or delete, then presumably consume the receipt via ricursor_action_consume. No explicit when-to-use, when-not-to-use, or alternative routing (e.g. group check for multiple actions) is stated. The 'Never send source' constraint is the only hard guidance given.

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