Skip to main content
Glama

LiquiLens Failure Radar

Markov forward odds per layer

forward_odds
Read-onlyIdempotent

Counted Markov transitions and empirical 5/20-day reach odds, withheld until 60 observed days; counts stay visible and absence is never precision. Historical frequencies are not calibrated forecasts. Display-only, never a state driver.

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": "forward_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine behavior beyond them: results are withheld until 60 observed days, counts remain visible during withholding, absence of an entry is not a precision claim, and the frequencies are uncalibrated. These are exactly the caveats an agent needs to avoid over-reading the output.

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?

Dense and front-loaded with four short clauses, no filler. The compression goes slightly too far, though: “absence is never precision” and “per layer” are cryptic enough that a reader must guess at the intended meaning.

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

Completeness3/5

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

With no output schema and no parameters, the description carries the full burden of explaining what comes back, and it partially does so by naming the two return concepts and the withholding behavior. What is missing is the output's shape and the meaning of “layer”, so an agent still cannot predict the response structure or scope.

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?

There are zero parameters, which normally sets a baseline of 4. The description adds no scoping information about what the tool operates on (which layers, which universe) despite the “per layer” framing, so it falls slightly short of the zero-param baseline.

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

Purpose3/5

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

The description names what is computed (counted Markov transitions, empirical 5/20-day reach odds) and a withholding rule, so the resource is identifiable. But “per layer” in the title is never explained, and with zero parameters it is unclear whether all layers are returned or only one. It does nothing to distinguish itself from the many *_board / *_coverage siblings, so an agent cannot confidently route between them.

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?

“Display-only, never a state driver” is a real usage constraint that tells the agent not to feed this into state logic, which is better than nothing. However, no alternative tool is named and no positive condition (“use this when you need X”) is given, so the when-to-use case is only implied.

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.