Skip to main content
Glama
Sign In

LiquiLens — the Failure Radar

by io.github.beepboop2025
OverviewDiscussionsAdmin

Co-op lending districts

lending_geography
Read-onlyIdempotent

Co-op operating areas and dated district environment. IDs: in-dccb-, in-stcb-, in-dist-, in-state-. No score.

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": {
      "id": "<id>"
    },
    "name": "lending_geography"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/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 bar is lower. The description adds two real facts beyond them: the accepted ID namespaces (in-dccb-, in-stcb-, in-dist-, in-state-) and that no score is returned. It still says nothing about pagination via offset, record shape, or how "dated" versions behave.

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 with no filler, and the resource statement is front-loaded. But the telegraphic fragments ("IDs: ...", "No score.") read as compressed notes rather than a coherent definition, leaving the reader to decode their intent.

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?

For a two-parameter lookup with zero schema description coverage and no output schema, the description should explain what a call returns and how offset paginates. Neither is addressed, so an agent cannot predict the response or page through results without trial and error.

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?

Schema description coverage is 0%, so the description must carry the load, and it does partially: it enumerates the four valid ID prefixes for the required id parameter, which is meaning the bare `string` type does not provide. The offset parameter, however, is never mentioned, so half the parameter set remains undocumented.

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?

"Co-op operating areas and dated district environment" names the resource but supplies no verb, so it is unclear whether the tool lists, looks up, or resolves geography records. The ID-prefix hints imply a lookup-by-identifier tool, but an agent must infer that. It is distinguishable from the board/evidence siblings mainly by topic, not by an explicit statement of function.

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 statement of when to use this tool versus the 25 siblings or versus universe_search/evidence_* tools. The only routing signal is the ID-prefix list, which indirectly implies "use when you already have one of these IDs," but that is left implicit. No exclusions or prerequisites are given.

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

All LiquiLens — the Failure Radar toolsInspect
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