Skip to main content
Glama

LiquiLens Failure Radar

Historical evidence: European named case files

evidence_europe
Read-onlyIdempotent

Seven cited European retrospective case files through unrecalibrated Indian lenses. Named case studies, not a cohort: no European recall percentage to quote.

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

Input Schema

NameRequiredDescriptionDefault
slugNocase-file slug, e.g. 'credit-suisse'; omit for all seven

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"case-file slug returned by the summaries, e.g. 'credit-suisse'; omit for all seven"New value: +"case-file slug, e.g. 'credit-suisse'; omit for all seven"
  2. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"optional kebab-case case-file slug, e.g. 'credit-suisse'; omit for all seven summaries"New value: +"case-file slug returned by the summaries, e.g. 'credit-suisse'; omit for all seven"
  3. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered; the description adds content-level context that the payload is exactly seven named case studies rather than a statistical cohort, which is genuinely beyond the annotations. It does not say how the cases are cited or what fields each file contains.

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?

Two short sentences with the count front-loaded, so nothing is padded. However, the second half is dense and cryptic ('unrecalibrated Indian lenses', 'European recall percentage') and costs more clarity than the brevity saves.

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 one optional parameter and no output schema, the definition should characterize the returned records; noting the files are 'cited' and 'named case studies, not a cohort' does part of that work. It still leaves the shape of a case file and the meaning of its sourcing frame undefined.

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 slug property already carries an example ('credit-suisse') plus the 'omit for all seven' default, so the description adds little. Its only contribution is restating the count of seven, which corroborates rather than extends the 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 identifies the resource as seven cited European retrospective case files and disambiguates the region versus evidence_india/evidence_us siblings, but it never states a verb (list, fetch, or compare) and the phrase 'through unrecalibrated Indian lenses' is unexplained jargon that obscures what the tool actually does.

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 clause 'no European recall percentage to quote' implies what the tool cannot give (aggregate statistics), which is useful negative guidance, but there is no positive statement of when to call this rather than evidence_india, evidence_us, or evidence_markets.

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.