Skip to main content
Glama

Report activity

ricursor_report

Record what an agent spent (usage) and what it changed (state).

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": {
      "request_id": "<request_id>"
    },
    "name": "ricursor_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
usageNo
projectNoProject name inside the workspace.
workspaceNoIgnored: the key already selects its workspace.
request_idYesUnique ID per logical report; reuse unchanged when retrying.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/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 burden of behavioral disclosure and mostly fails to. It does not say whether the call mutates stored state, whether reports are idempotent on retry, or how partial usage/state payloads are handled, all of which matter for a tool whose schema centers on request_id reuse.

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 sentence with no filler, and the two core payloads are front-loaded. It is efficient, though its brevity edges into under-specification rather than model conciseness.

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 five-parameter tool with two nested objects, an enum-bearing state payload, and no output schema, one sentence is not enough. Nothing tells the agent what a successful report returns or how the write behaves, so the definition is incomplete relative to the tool's complexity.

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?

The parenthetical glosses ("usage" = what was spent, "state" = what was changed) do add meaning beyond the schema for the two nested objects. With 60% schema description coverage, the remaining fields (project, workspace, request_id) are documented in the schema itself, so the description's thin parameter treatment is tolerable but adds little.

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 uses a concrete verb ("Record") and names the two payloads being recorded, usage and state, so an agent knows this is the write-side reporting tool. It does not name or differentiate itself from siblings such as ricursor_ledger or ricursor_check, which keeps it short of a 5.

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 explicit statement of when to call this tool versus the many ricursor_action_* and ricursor_check siblings, nor any prerequisite or sequencing guidance. The only implied usage comes from the word "Record", leaving the agent to infer that this is the post-work reporting step.

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