claimidx

Official

by claimidx

Overview Schema Source Related Servers Discussions Admin

Python

Local

Ask the remote ledger

claimidx_home_ask

Read-onlyIdempotent

Rank a raw error against the public ledger to preview known fixes without importing or writing local state. Use when the local index is empty or stale.

Instructions

Rank a raw error against the remote public ledger over HTTP without importing it or writing any local state. No DID needed. Use when the local index is empty or stale and you want a look before claimidx_home_pull; prefer claimidx_ask for normal work because it also sees your own claims and records the ask. Returns url, hit, n, pool, skipped_n, claims (each with own and src=home).

Input Schema

TableJSON Schema

Name	Required	Description
`k`	No	Maximum claims to return (default 5).
`rt`	No	Runtime as name@version, e.g. py@3.12 or node@20.18.2 (only the major is kept). Omit if unknown.
`dep`	No	Packages involved as name@version, e.g. ["next@15.0.0"]. The same package at another version still ranks as a similar hit.
`eco`	No	Package ecosystem the failure occurred in: py, npm, go, rust, java, mcp, browser, ci, or other. Narrows the fingerprint; omit if unknown.
`err`	Yes	Raw error text exactly as the tool or compiler printed it (stderr line, traceback tail). Do not pre-normalize; Claimidx fingerprints it.
`url`	No	Ledger to read: HTTP(S) URL, file: URL, or local jsonl path. Defaults to CLAIMIDX_HOME (the public GitHub ledger).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`n`	No
`hit`	No
`url`	No
`pool`	No
`claims`	No
`skipped_n`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.7Sep 19, 2026

changedInput schema / properties / eco / description

Previous value: -"Package ecosystem the failure occurred in: py, npm, go, cargo, docker, other. Narrows the fingerprint; omit if unknown."New value: +"Package ecosystem the failure occurred in: py, npm, go, rust, java, mcp, browser, ci, or other. Narrows the fingerprint; omit if unknown."

Changed7 schema fields changedv0.7.6Sep 15, 2026

addedInput schema / properties / dep / description

Added value: +"Packages involved as name@version, e.g. [\"next@15.0.0\"]. The same package at another version still ranks as a similar hit."

addedInput schema / properties / eco / description

Added value: +"Package ecosystem the failure occurred in: py, npm, go, cargo, docker, other. Narrows the fingerprint; omit if unknown."

addedInput schema / properties / err / description

Added value: +"Raw error text exactly as the tool or compiler printed it (stderr line, traceback tail). Do not pre-normalize; Claimidx fingerprints it."

addedInput schema / properties / k / description

Added value: +"Maximum claims to return (default 5)."

addedInput schema / properties / rt / description

Added value: +"Runtime as name@version, e.g. py@3.12 or node@20.18.2 (only the major is kept). Omit if unknown."

addedInput schema / properties / url / description

Added value: +"Ledger to read: HTTP(S) URL, file: URL, or local jsonl path. Defaults to CLAIMIDX_HOME (the public GitHub ledger)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "claims": {
+      "type": "array"
+    },
+    "hit": {
+      "type": "boolean"
+    },
+    "n": {
+      "type": "integer"
+    },
+    "pool": {
+      "type": "integer"
+    },
+    "skipped_n": {
+      "type": "integer"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv0.6.1Sep 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false; the description adds meaningful behavioral context beyond that: no local state is written, no DID is needed, the ledger is accessed over HTTP, and returned claims include own/src=home. This complements rather than merely repeats 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?

The description is compact, front-loaded with the core action, then usage guidance, then return shape. Every sentence carries distinct information and there is no filler or repetition of the tool title.

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 tool has six parameters, an output schema, and a large sibling family, the description covers all essentials: what it does, when to use it, which alternatives to prefer, safety/state behavior, auth needs, and return value shape. Nothing critical is missing for correct selection and invocation.

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 all six parameters are already documented in the schema. The description adds one useful non-schema nuance about returning claim fields, but it does not substantially extend parameter-level meaning beyond what the schema already provides.

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 opens with a specific verb and resource: 'Rank a raw error against the remote public ledger over HTTP'. It clearly distinguishes itself from siblings by stating it does not import or write local state and explicitly contrasts with claimidx_home_pull and claimidx_ask.

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?

The description gives explicit when-to-use guidance: 'Use when the local index is empty or stale and you want a look before claimidx_home_pull', and names the preferred alternative, claimidx_ask, with the reason it is preferred. No inference is left to the agent.

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