Skip to main content
Glama

The Durability Curve

by com.durabilitycurve
OverviewDiscussionsAdmin

Get a claim ledger

get_claim_ledger
Read-onlyIdempotent

Get the claim ledger for one essay: each load-bearing claim it makes, the source it was checked against, the quoted words, where in the source they appear, the date the source was read, and a status saying how the claim was checked. The response defines every status. Filter by claim ids or status, or ask for compact rows. Claims removed during checking are listed separately under "struck", with the reason; they are not claims the essay makes. Only some essays have a ledger: search results and get_essay link to one when it exists. These tools retrieve The Durability Curve's public material. They do not certify that any claim is true.

Input Schema

NameRequiredDescriptionDefault
idsNoOnly these claim IDs, e.g. ["SL1", "SL6"].
slugYesThe essay's site or Substack slug (case-insensitive), or its full durabilitycurve.com/blog/ or harryfloyd.substack.com/p/ URL.
statusNoOnly claims with this status, by its key or label (e.g. "VERIFIED" or "Verified"); the response lists every status.
compactNotrue: each claim as id, status, claim, source, source_url, locator and date_read only (no quoted words or essay sentence).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
+  "default": false,
+  "description": "true: each claim as id, status, claim, source, source_url, locator and date_read only (no quoted words or essay sentence).",
+  "type": "boolean"
+}
    • addedInput schema / properties / ids
      Added value: +{
+  "description": "Only these claim IDs, e.g. [\"SL1\", \"SL6\"].",
+  "items": {
+    "maxLength": 20,
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Only claims with this status, by its key or label (e.g. \"VERIFIED\" or \"Verified\"); the response lists every status.",
+  "maxLength": 40,
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"The essay's slug, as in durabilitycurve.com/claims/<slug>/. Get it from search."New value: +"The essay's site or Substack slug (case-insensitive), or its full durabilitycurve.com/blog/ or harryfloyd.substack.com/p/ URL."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the response defines every status, struck claims are returned separately with reasons and are not claims the essay makes, and the tool does not certify truth — real epistemic caveats beyond the structured fields.

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?

It is front-loaded with what the tool returns and the field list before moving to filtering and caveats, so an agent can act on the first sentence. The final two sentences about retrieval and truth-certification are slightly editorial but still earn their place as scope warnings.

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?

With no output schema, the description carries the return-shape burden and does so well, describing the per-claim fields, the separate 'struck' collection, and that statuses are self-documenting. It stops short of saying what actually happens for an essay with no ledger (error versus empty result), which is the remaining gap.

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 100% with per-parameter descriptions for ids, slug, status, and compact, so the schema does the heavy lifting and the baseline is 3. The description's 'Filter by claim ids or status, or ask for compact rows' restates what the schema already documents without adding syntax or edge-case detail.

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 and resource ('Get the claim ledger for one essay') and then enumerates exactly what a ledger row contains: claim, source, quoted words, locator, date read, status. It also separates itself from siblings by pointing to search results and get_essay as the way to discover whether a ledger exists.

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

Usage Guidelines4/5

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

Gives a clear availability condition ('Only some essays have a ledger: search results and get_essay link to one when it exists'), which tells the agent how to reach this tool and when it will be useful. It lacks an explicit when-not-to-use statement or a direct contrast with get_essay's own content, which keeps it short of a 5.

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

All The Durability Curve toolsInspect
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.

Resources