Skip to main content
Glama

The Durability Curve

by com.durabilitycurve
OverviewDiscussionsAdmin

Search The Durability Curve

search
Read-onlyIdempotent

Search or list the public archive of The Durability Curve: essays on which kinds of work keep their value as AI gets cheaper, the checked claims in each essay's claim ledger, the dated calls printed in The Durability Curve Weekly, the five laws and two derived principles the essays are tested against, and the free tools. With a query, returns ranked matches, each with its kind (essay, claim, call, law or tool), a snippet and the canonical URL; "title_matched" says whether any essay title contains every word of the query. With an empty query, lists newest first, filtered by kind, series or has_ledger, and "total" counts every match. Read a match in full with get_essay, get_claim_ledger or get_weekly_calls. These tools retrieve The Durability Curve's public material. They do not certify that any claim is true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoOnly this kind of result: essay, claim, call, law (the framework's laws and principles) or tool (the free tools). A list (empty query) defaults to essays.
sortNorelevance (default for a query) or newest. A list is always newest first.
limitNoHow many results to return, 1 to 25. Default 5.
queryNoWhat to look for, in plain words, e.g. "agent reliability", "memory chip deposits" or a call ID like "W02-5". Leave empty to LIST instead (newest first), with the filters below.
seriesNoOnly essays (and their claims) in this series, e.g. "The Blueprint". Case does not matter.
has_ledgerNotrue: only essays that have a claim ledger. false: only essays without one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Only this kind of result. A list (empty query) defaults to essays."New value: +"Only this kind of result: essay, claim, call, law (the framework's laws and principles) or tool (the free tools). A list (empty query) defaults to essays."
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "essay",
-  "claim",
-  "call"
-]New value: +[
+  "essay",
+  "claim",
+  "call",
+  "law",
+  "tool"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, but the description goes further by disclosing the return shape (kind, snippet, canonical URL), the meaning of title_matched and total, and an important epistemic caveat that results are not certified as true.

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?

Front-loaded with the scope of the archive before detailing query vs list behavior, and every sentence carries information. It is dense as a single block and slightly long, but there is little 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?

There is no output schema, so the description compensates by describing the match fields and the total counter, plus the query-vs-list duality. For a six-parameter read tool with no output schema, nothing essential is missing.

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% and every parameter is already documented with enums, defaults, bounds and examples. The description mostly restates those semantics (empty query lists, kind filtering) rather than adding new syntax or constraints, 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 (search or list) and enumerates the exact resources covered: essays, claim ledgers, weekly calls, laws/principles, and tools. It also names the sibling tools used to read a match in full, so an agent can distinguish search from retrieval without opening a 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?

Explicitly branches on the query parameter: a non-empty query returns ranked matches, an empty query lists newest-first filtered by kind/series/has_ledger. It names the alternatives (get_essay, get_claim_ledger, get_weekly_calls) and when to escalate to them.

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