Skip to main content
Glama
Sign In
stalemap

stalemap

by Umair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Is the stalemap block in AGENTS.md / CLAUDE.md current?

check_notes
Read-only

Verifies whether your project's stalemap notes block is missing or out of date for current dependencies and model. Detects outdated API usage so coding agents can refresh guidance.

Instructions

Check whether the project's stalemap notes block is missing or out of date for the current dependencies and model. Offline and fast.

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": "check_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoProject directory (default: the server's working directory)
modelNoYour own model id (e.g. claude-opus-5-5). Defaults to the model configured in the coding agent's settings.
cutoffNoTraining cutoff (YYYY-MM or YYYY-MM-DD) to use instead of a model id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower, and the description does add one genuine behavioral fact beyond annotations: the check is offline and fast. It stops short of saying what the check actually returns (boolean, diff, suggested patch) or whether it writes or repairs anything, which matters for a tool whose name implies only inspection.

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 with zero filler; the object of the check is front-loaded and the cost/latency note is a compact trailing clause. Nothing could be cut without losing information.

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?

With no output schema and zero required parameters, the description carries the burden of saying what a caller gets back and what to do with a 'stale' result; it says neither. It is otherwise sufficient for invoking the tool correctly, since all three parameters are documented in the schema.

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 100%, so cwd, model, and cutoff are fully documented in the schema itself; baseline is 3. The description adds no syntax, format, or precedence guidance (e.g. model vs cutoff interaction) beyond what the schema already states.

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?

Names a specific verb ('Check whether') and a specific resource ('the project's stalemap notes block'), with the condition tested ('missing or out of date for the current dependencies and model'). The title supplies the concrete file locations (AGENTS.md / CLAUDE.md) that the description only implies, and no sibling (search_changes, package_changes, project_changes) is named to sharpen 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?

'Offline and fast' implies this is a cheap, safe pre-flight check that can be run freely, which is weak but real usage guidance. There is no explicit statement of when to run it versus the change-listing siblings, and no stated prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools