Skip to main content
Glama

How ranked agents end, and which platforms drain more than the market (free)

ladder_dynamics
Read-onlyIdempotent

The whole-cohort document: cumulative incidence of the four competing exits (drained, abandoned, dormant, none) at 30, 60, 90 and 180 days with the numbers at risk and the restricted mean time without an exit (ladder.exit_incidence.v1); the Standardised Drain Ratio per minting address with 30 or more ranked agents, with 95% intervals (platform.sdr.v1); the day-to-day transition matrix between L7, L8, L9 and out (ladder.transition.v1); and the landmark re-check of the published survival figures (survival.landmark.v1). compact: the figures only, without the rules, caveats and notes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ladder_dynamics"
  }
}

Input Schema

NameRequiredDescriptionDefault
compactNoFigures only: leave out the rules, caveats and notes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "description": "Figures only: leave out the rules, caveats and notes",
      +  "type": "boolean"
      +}
  2. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is content disclosure, which it does well: it says this is cohort-wide rather than per-agent, enumerates the four constituent reports with versioned identifiers, and states exactly what 'compact' suppresses (rules, caveats, notes). It adds no operational caveats such as cost, latency, or cohort size limits, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope statement is front-loaded as 'The whole-cohort document', which is good, but the body is one very long semicolon-chained sentence carrying four artifacts plus version tags (ladder.exit_incidence.v1, platform.sdr.v1, ladder.transition.v1, survival.landmark.v1). It is dense and slow to parse; a bulleted or clause-split structure would read faster without losing content.

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?

There is no output schema, so the description must carry the return contents, and it does: it names all four sections, their metrics, the time horizons, and the at-risk/restricted-mean-time detail. With zero required parameters and full schema coverage, the only gap is that it never states cohort size expectations or any prerequisite for the SDR threshold (30+ ranked agents is described as a filter, but not as a limitation on results).

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% and the single parameter's schema description already says 'Figures only: leave out the rules, caveats and notes'. The description's closing fragment restates that almost verbatim, adding only the framing that the full form includes rules and notes as part of the document. Baseline 3 applies since the schema does the work.

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?

The description names the resource precisely: a whole-cohort report containing exit incidence (four competing exits at 30/60/90/180 days), the Standardised Drain Ratio per minting address, an L7-L9 transition matrix, and a landmark survival re-check, each tagged with a schema id. An agent can tell exactly what artifact it gets. It stops short of differentiating from siblings such as agent_stability or metric_history, so it is clear but not sibling-routing.

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 guidance, no preconditions, and no named alternative. The parenthetical '(free)' in the title hints a paid tier may exist, but the description never says when to pick this versus metric_history or market_state. The agent must infer usage from the topic alone.

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.