Skip to main content
Glama

The Durability Curve

by com.durabilitycurve
OverviewDiscussionsAdmin

Get an essay

get_essay
Read-onlyIdempotent

Get one Durability Curve essay: by default its full public text as markdown, with its title, dates, canonical field, access, length, sections, tools and a link to its claim ledger when it has one. A long essay can be read in parts: part "outline" lists the sections with their opening lines, part "section" returns one, and part "meta" returns everything but the text. For a part-paid essay only the free part is public, and the text says where it stops. The canonical field is the address to cite. These tools retrieve The Durability Curve's public material. They do not certify that any claim is true.

Input Schema

NameRequiredDescriptionDefault
partNofull (default): the whole public text. meta: dates, length, access, sections, tools and a content hash, without the text. outline: each section's heading, length and opening lines. section: one section's text (name it with section).full
slugYesThe essay's site or Substack slug (case-insensitive), or its full durabilitycurve.com/blog/ or harryfloyd.substack.com/p/ URL.
sectionNoWith part "section": the section's number from the outline (0 is the opening, before the first heading) or words from its heading.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / part
      Added value: +{
+  "default": "full",
+  "description": "full (default): the whole public text. meta: dates, length, access, sections, tools and a content hash, without the text. outline: each section's heading, length and opening lines. section: one section's text (name it with section).",
+  "enum": [
+    "full",
+    "meta",
+    "outline",
+    "section"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / section
      Added value: +{
+  "description": "With part \"section\": the section's number from the outline (0 is the opening, before the first heading) or words from its heading.",
+  "maxLength": 200,
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"The essay's slug: the last part of its address, as in durabilitycurve.com/blog/<slug>/. Lowercase letters, digits and hyphens. 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.9/5.0
Behavior5/5

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

Beyond the safety hints (readOnly/idempotent), the description provides critical operational behavior, such as the limitation on paywalled content (only the free part is public) and a mandatory disclaimer that the tool does not certify facts.

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?

The description is very dense and lengthy, but every sentence serves a distinct function (content list, part function, paywall constraint, disclaimer). The high information density makes the length well-justified.

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's complexity—retrieving various parts of content under specific external constraints (paywalls)—the description is exceptionally complete, leaving no major ambiguity for the AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the schema is complete (100% coverage), the description adds vital semantic context: it clarifies that 'slug' can be a full URL or a short identifier, and it explains the exact contents of the enum values for 'part'.

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 explicitly states the resource it handles (Durability Curve essays) and details exactly what information is returned (title, dates, canonical field, sections), clearly defining its scope.

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?

It provides explicit instructions on choosing the `part` parameter (e.g., use 'outline' for sections, 'meta' for data without text) and manages user expectations regarding paywalled content.

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