The Durability Curve

Get the weekly calls

get_weekly_calls

Read-onlyIdempotent

Get the calls printed in The Durability Curve Weekly: dated, checkable predictions, each with the confidence printed at the time and the date or event it resolves on. Filter by status, ID, issue, resolution date or printed confidence. The wording is exactly as printed and never changes after publication. outcome is null until a call resolves. counts describe the calls returned; record describes every call. These tools retrieve The Durability Curve's public material. They do not certify that any claim is true.

Input Schema

Name	Required	Description	Default
`id`	No	One call by its ID, e.g. "W02-5".
`issue`	No	Only the calls printed in this issue of the Weekly.
`status`	No	open, resolved or all (default).	all
`resolves_after`	No	YYYY-MM-DD. Only calls whose latest resolution date is after this day, earliest first.
`resolves_before`	No	YYYY-MM-DD. Only calls whose latest resolution date is before this day, earliest first. A call that resolves on an event "or" a date counts by that date.
`confidence_at_most`	No	Only calls printed at this confidence or lower, in percent, e.g. 30.
`confidence_at_least`	No	Only calls printed at this confidence or higher, in percent, e.g. 60.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 23, 2026

addedInput schema / properties / confidence_at_least

Added value: +{
+  "description": "Only calls printed at this confidence or higher, in percent, e.g. 60.",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / confidence_at_most

Added value: +{
+  "description": "Only calls printed at this confidence or lower, in percent, e.g. 30.",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / id

Added value: +{
+  "description": "One call by its ID, e.g. \"W02-5\".",
+  "maxLength": 12,
+  "type": "string"
+}

addedInput schema / properties / issue

Added value: +{
+  "description": "Only the calls printed in this issue of the Weekly.",
+  "maximum": 999,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / resolves_after

Added value: +{
+  "description": "YYYY-MM-DD. Only calls whose latest resolution date is after this day, earliest first.",
+  "maxLength": 20,
+  "type": "string"
+}

addedInput schema / properties / resolves_before / maxLength
```
Added value: +20
```
removedInput schema / properties / resolves_before / pattern
```
Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
```

First observedOct 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behaviour, so the bar is lower, and the description still adds real substance: the printed wording never changes after publication, outcome is null until a call resolves, and counts versus record describe different result scopes. The closing disclaimer that the tools do not certify any claim is true is a meaningful trust caveat not derivable from annotations.

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 resource and its defining traits, then filters, then result-shape notes. It is slightly padded by the two-sentence disclaimer tail, but every sentence carries information rather than filler.

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 accepts the burden of explaining returns and does so adequately: outcome nullity before resolution, and the counts-versus-record distinction, plus the immutability of printed wording. Only the absence of any guidance on result volume or default ordering against siblings keeps it short of full coverage.

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%, so every one of the seven parameters is already documented with examples and formats, and the description largely enumerates the same filter set. The one piece of added meaning – that a call resolving on an event 'or' a date is counted by the date – is mirrored in the schema for resolves_before, so the description adds little beyond structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource – calls printed in The Durability Curve Weekly – and adds their defining nature (dated, checkable predictions with confidence at time of printing). That is far more than a restatement of the name. It does not, however, contrast itself with the closest sibling, get_claim_ledger, which an agent could plausibly confuse with this.

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

Usage Guidelines3/5

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

It lists what can be filtered on (status, ID, issue, resolution date, printed confidence), which implies when to reach for this tool, but gives no explicit when-not conditions and no pointer to an alternative among get_claim_ledger, get_essay, related_to or search.

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 tools Inspect

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

Need Help?