Skip to main content
Glama

LiquiLens Failure Radar

Latest evidence-led article

latest_article
Read-onlyIdempotent

Today's exact full-text LiquiLens editorial: current institution-risk analysis when the evidence moved, else a labelled historical replay. Quote it with its evidence clock and passing publication receipt, without regenerating facts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety and idempotency, while the description adds meaningful behavioral context: exact full-text retrieval, fallback to a labelled historical replay, quoting with an evidence clock and publication receipt, and no fact regeneration. This is useful beyond the annotation profile, though authentication or rate-limit details are absent.

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?

The description is compact and front-loads the core resource before adding freshness, fallback, and citation details. It is slightly dense with jargon such as 'evidence clock' and 'passing publication receipt,' but no sentence is clearly wasted.

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?

For a zero-parameter, read-only tool with no output schema, the description gives enough detail about what is returned: full-text editorial content, current versus historical replay labeling, and provenance through an evidence clock and publication receipt. It could more fully specify the response shape or sibling routing, but it is largely complete.

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 has zero parameters, so there is no parameter semantics burden and the baseline of 4 applies. The description does not need to explain parameters and correctly focuses on returned content and provenance instead.

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 clearly states the resource: 'Today's exact full-text LiquiLens editorial,' and explains that it is current institution-risk analysis when evidence moved or a labelled historical replay otherwise. It is specific enough to distinguish the content type, though it does not explicitly contrast itself with sibling evidence tools.

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?

The description implies usage by describing freshness behavior ('when the evidence moved, else a labelled historical replay'), but it does not say when to choose this tool over siblings such as evidence_institution, institution_evidence_monitor, or verify_published_record. Guidance is present but indirect.

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.