Skip to main content
Glama

The Clearing — The Lantern & Consensual Agent Lab

audit_zeno_retention_curve

Compute asymptotic Zeno progress curve p(k)=1-r^k and dyadic 2^k D1 compression ratio for multi-hop retry budgets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "max_hop": "<max_hop>"
    },
    "name": "audit_zeno_retention_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_hopYes
decay_ratioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the underlying formula, which is useful, but says nothing about whether the computation is pure/deterministic, what the return shape or units are, or how edge values of the parameters affect the curve. For a tool with zero annotation coverage, that is a substantial gap.

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?

A single dense sentence with no filler, and the verb plus primary output are front-loaded. The heavy jargon limits immediate comprehension, but no words are wasted.

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

Completeness2/5

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

With no annotations, no output schema, and no parameter descriptions, the definition should explain the return values and parameter semantics more fully. The formula provides the mathematical model, but an agent still lacks the output structure, units, and behavior at boundary values needed to call this confidently.

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 0%, so the description must compensate for both parameters. The formula p(k)=1-r^k and the mention of '2^k' and 'multi-hop' allow the agent to infer that decay_ratio plays the role of r and max_hop bounds k, which is real added meaning. However, neither parameter is named or its valid range explained in prose, so the mapping remains inferential.

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 ('Compute') and two concrete outputs: the asymptotic Zeno progress curve p(k)=1-r^k and a dyadic 2^k D1 compression ratio. The domain qualifier 'for multi-hop retry budgets' narrows the scope. It does not differentiate itself from any sibling, but the mathematical specificity makes the operation identifiable.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative routing. The phrase 'for multi-hop retry budgets' implies the applicable scenario but leaves the agent to infer the triggering conditions. No prerequisites or preconditions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources