Skip to main content
Glama

Save verified correction

ricursor_correct

After Ricursor blocks a check, save the one-sentence lesson so every agent on this project gets it. Only accepted for your own blocked action from the last 24 hours.

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>",
      "action_id": "<action_id>",
      "rule": "<rule>"
    },
    "name": "ricursor_correct"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleYes
projectYesProject name inside the workspace.
action_idYesaction_id or group_id of the blocked check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare openWorldHint=false, so the description carries the behavioral load, and it does well: it discloses the precondition (a prior block), the eligibility rule (own action, 24-hour window), and the blast radius ('every agent on this project gets it'). It leaves out whether the saved lesson is immutable/deletable and what a rejection looks like.

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?

Two short sentences: effect and audience first, then the eligibility constraint. No redundant restatement of the tool name, and every clause adds an actionable detail.

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

Completeness4/5

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

For a three-parameter write tool with no output schema, the description covers trigger, eligibility, and downstream effect adequately. The remaining gap is write-specific behavior — permanence, edit/delete, and failure mode — which matters more here because only openWorldHint is annotated.

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

Parameters4/5

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

Schema coverage is 67%, with `rule` having no schema description; the definition fills that gap by specifying it is a 'one-sentence lesson'. It also constrains `action_id` to 'your own blocked action', which the schema only calls the id or group_id of the blocked check.

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 and resource: 'save the one-sentence lesson', tied to a concrete trigger ('After Ricursor blocks a check'). The trigger phrase also implicitly separates it from the check/consume siblings, though no sibling is named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear activation condition ('After Ricursor blocks a check') plus a hard acceptance gate ('Only accepted for your own blocked action from the last 24 hours'). It does not name an alternative tool for recording non-correction information (e.g. the ledger), so there is no explicit when-not 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