Skip to main content
Glama

Serve context

ricursor_context
Read-only

The verified corrections and recent file changes an agent must respect before it writes code.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ricursor_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoTask to retrieve relevant rules for.
limitNo
sinceNoPrevious cursor for this same key, project and task; returns changed rules and removed IDs.
projectNoProject name inside the workspace.
workspaceNoIgnored: the key already selects its workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description contributes a trust framing ('verified') and an ordering constraint ('must respect'), but says nothing about result shape, delta semantics, or what an unfiltered call returns — with zero required parameters that is a notable omission.

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 14-word sentence fragment with no filler — nothing to trim. It is held back only by being a fragment rather than a front-loaded action statement, which weakens immediate comprehension.

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?

A five-parameter tool with no output schema, no required parameters, and no explanation of what a default call returns. Since the schema and annotations cannot convey the delta/incremental-refresh workflow or the meaning of an unscoped call, the description needed to do that work and does not.

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 coverage is 80%, so the schema largely documents the parameters itself, establishing a baseline of 3. The description adds no parameter meaning at all — it never mentions `task` scoping, `limit` paging, or the `since` cursor's changed-rules/removed-IDs behavior, which is exactly the kind of semantic an agent would benefit from hearing in prose.

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 description names a specific resource set — verified corrections plus recent file changes — so it is more than a restatement of the title 'Serve context'. But it is a bare noun phrase with no verb, never saying 'retrieve' or 'returns', and it does not distinguish itself from siblings like ricursor_check or ricursor_snapshot. An agent can guess it is a read of rule context, but only by inference.

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?

The clause 'before it writes code' gives a clear temporal trigger for calling it, which is real guidance. However, no alternatives are named and there is no when-not guidance — nothing tells the agent whether to use ricursor_check or ricursor_snapshot instead for overlapping needs.

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