Skip to main content
Glama

Propose related changes

ricursor_action_group_check

Metadata-only decision for up to 20 related JS/TS writes/deletes judged on their combined end state (moves, renames).

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>",
      "group_id": "<group_id>",
      "actions": "<actions>"
    },
    "name": "ricursor_action_group_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionsYes
projectYes
group_idYesUnique per proposed action, 8-80 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations provide only openWorldHint=false, so the description must carry most of the behavioral burden. 'Metadata-only' usefully signals that no files are actually mutated, but the description says nothing about whether the decision approves/rejects, what happens to rejected actions, idempotency, or what the response contains — significant gaps for a gatekeeping tool.

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?

One tight sentence with no filler, and the size limit and batch semantics are front-loaded. It is arguably too terse rather than too long, but nothing is wasted.

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?

Three required parameters, no output schema, and only a single annotation mean the description has to do heavy lifting, and it does not. The meaning of 'decision', the role of project, and what the agent gets back are all missing, leaving the tool callable but not reliably interpretable.

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 description coverage is 33%: only group_id is documented, and only inside the schema. The description does add real meaning for the actions array (related writes/deletes judged as a combined end state, up to 20), which is more than the schema says. But the project parameter and the group_id-to-actions relationship remain unexplained in both places.

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 sentence names a scope (up to 20 related JS/TS writes/deletes judged on combined end state) and mentions moves/reNames, so the agent can infer it evaluates a batch as a unit. But 'metadata-only decision' is vague about the verb — is it validating, simulating, approving, or blocking? It also does not differentiate itself from siblingricursor_action_group_consume or ricursor_action_check, so selection remains uncertain.

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?

No explicit when-to-use statement, no prerequisites, and no named alternative. The phrase 'judged on their combined end state' hints that this is the batch-level counterpart to per-action checking, but the agent must infer that from the sibling names rather than from the text.

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