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 a remote public ledger over HTTP without importing it locally. Use when the local index is empty or stale to preview known failures before pulling.

Instructions

Rank a raw error against the remote public ledger over HTTP without importing the ledger into the local index. Auto-mints a local DID when OWNER unset and logs an ask event; returns path_b (ask alone is not a countable commons DID — follow path_b.next: first hold cix_bdc82291f2fbb06a on py@3.13, then claim --yes --share-yes). 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. Returns url, hit, n, pool, skipped_n, claims (each with own and src=home), path_b.

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
`path_b`	No
`skipped_n`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.13Sep 26, 2026
- addedOutput schema / properties / path_b
```
Added value: +{
+  "type": "object"
+}
```

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

A3.6/5.0

Behavior1/5

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

The description explicitly discloses write side effects ('Auto-mints a local DID when OWNER unset and logs an ask event'), which contradicts the annotations' readOnlyHint=true (no environment modification) and idempotentHint=true (repeated calls log additional ask events). Per the rubric, a description that contradicts annotations scores 1.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the second sentence is a run-on that embeds procedural CLI instructions ('hold cix_... on py@3.13, then claim --yes --share-yes') and then re-enumerates the return fields already covered by the output schema. Signal-to-noise degrades after the first sentence.

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

Completeness4/5

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

An output schema exists, so return fields need not be listed (the description does so redundantly but harmlessly). Purpose, usage, alternative selection, and side effects are all covered for a moderately complex read tool; only the dense path_b jargon could leave an agent unsure how to act.

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 the schema already documents all six parameters, including err normalization and rt packing. The description adds only environmental context ('OWNER unset'), not parameter syntax or format beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb+resource+mechanism: 'Rank a raw error against the remote public ledger over HTTP without importing the ledger into the local index.' It explicitly distinguishes itself from claimidx_ask ('also sees your own claims') and claimidx_home_pull, so an agent can route without opening either schema.

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?

Gives both the trigger condition ('use when the local index is empty or stale and you want a look before claimidx_home_pull') and a named alternative with the reason to prefer it ('prefer claimidx_ask for normal work because it also sees your own claims'). When/when-not/alternative are all present.

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