Skip to main content
Glama

LiquiLens Failure Radar

Crypto Regime board (BTC/ETH)

crypto_regime_board
Read-onlyIdempotent

BTC/ETH change points, log-SR, shifts and counts; disclosed bank exposure context. REST has paths. No institution score or investment advice.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds a scope boundary (no institution score, no investment advice) and notes disclosed bank exposure context, which is useful, but it does not explain what the board returns, how fresh the data is, or what "REST has paths" implies operationally.

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?

It is short and front-loads the BTC/ETH scope, which is good, but the text is telegraphic fragments separated by semicolons and includes "REST has paths", a phrase that carries no discernible meaning for an agent. The disclaimer sentence earns its place; the REST fragment does not.

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, the description must convey what comes back, and it does list content categories (change points, log-SR, shifts, counts, bank exposure context) — but several are undefined jargon, so an agent still cannot predict the response shape. For a zero-parameter read-only board, this is adequate but leaves real gaps.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to clarify; the baseline for a no-parameter tool applies. Nothing in the description contradicts or muddies the empty schema.

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 enumerates content areas ("change points, log-SR, shifts and counts" plus "disclosed bank exposure context") for BTC/ETH, which signals the resource, but it never uses a verb such as 'returns' or 'reports' and leaves jargon like "log-SR" undefined. An agent can roughly tell this is a crypto regime dashboard distinct from exposure/rails boards, but the purpose is stated as a noun fragment rather than a clear action.

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?

The only guidance-like content is a scope disclaimer ("No institution score or investment advice") and the cryptic "REST has paths", neither of which tells an agent when to pick this board over siblings like crypto_exposure_board or stablecoin_rails_board. There are no when-to-use or when-not-to-use conditions.

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.