Indraft

list_stale_records

Read-only

Records nobody has touched for a while, quietest first, with how many days each has been quiet. Use this to find what has stopped being maintained: the change feed tells you what DID happen, and this tells you what did not. Returns a list and dates, never a score.

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

Input Schema

Name	Required	Description
`limit`	No	How many to return. The page bound is published in the schema call, and asking for more is refused rather than quietly truncated.
`objectType`	No	What is being counted: a canonical type, or the key of a type this workspace defined.
`quietForDays`	No	How long counts as quiet. A record nobody has ever touched is the quietest of all and is included, rather than being excluded by a join.

Output Schema

Name	Required	Description	Default
`items`	Yes
`counts`	Yes
`quietForDays`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 1, 2026

addedInput schema / properties / limit / description

Added value: +"How many to return. The page bound is published in the schema call, and asking for more is refused rather than quietly truncated."

addedInput schema / properties / objectType / description

Added value: +"What is being counted: a canonical type, or the key of a type this workspace defined."

addedInput schema / properties / quietForDays / description

Added value: +"How long counts as quiet. A record nobody has ever touched is the quietest of all and is included, rather than being excluded by a join."

First observedSep 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses ordering ('quietest first'), output type ('a list and dates'), and a key boundary ('never a score'). It implies no mutation or side effects, consistent with the annotations.

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?

Three short sentences, front-loaded with the core behavior, then a use-case distinction, then a return-shape clarification. No redundancy or filler.

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

Completeness5/5

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

Given the rich parameter schema and the presence of an output schema, the description covers what an agent needs to select the tool and know what it will return. Optional-parameter behavior is fully documented in the schema, so the description is complete without duplicating it.

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 input schema already describes all three parameters in detail, including limit bounds, objectType semantics, and how quietForDays treats never-touched records. The description adds no extra parameter-level meaning, so the baseline 3 for full schema coverage is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool returns stale records ordered quietest-first with days of quiet, and explicitly contrasts itself with the change feed ('what DID happen' vs 'what did not'). This gives an agent a precise sense of the resource and result, and differentiates it from sibling listing tools.

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

Usage Guidelines5/5

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

'Use this to find what has stopped being maintained' is an explicit invocation context, and the change-feed contrast tells the agent when to prefer this tool over the activity-tracking sibling. The when/when-not decision is effectively encoded in one sentence.

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

All Indraft tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.