Skip to main content
Glama

tru8_check

Evidence research for a factual claim or article URL.

Submit a claim as text or paste an article URL. URLs are auto-detected
and trigger article mode: the pipeline extracts claims from the page
and auto-selects up to 5 for evidence research.

Tiers (in fallback order):
- lookup    (~£0.02, instant) — cached prior analysis
- consensus (~£0.03, instant) — cross-user aggregate landscape (k≥3 checks)
- quick     (~£0.07, ~15s) — web search + heuristic classification
- full      (~£0.15, ~60-90s) — web + specialist APIs, LLM classification, coverage recovery

Charges based on tier actually executed, not tier requested.
Identical calls within ten minutes return the same check, so a
transport retry never runs — or charges — twice.
Set max_tier to control maximum spend per call.

Output structure:
- claims[].claimMap.elements[] — verifiable sub-claims with state
  (supported/disputed/unresolved)
- claims[].claimMap.elements[].evidenceRefs[] — evidence mapped to elements
  with relationship (supports/challenges/context) and reasoning
- claims[].evidence[] — sources classified by tier (primary/reporting/
  commentary) and type (data/official/news/analysis/opinion/academic)
- claims[].claimMap.orientation — mechanical summary from element states
- _meta — execution metadata: executedTier, chargedPence, limitations

Per-argument guidance lives on the parameters themselves (see the
Annotated/Field declarations above), which is where a client can actually
read it — a docstring "Args:" block never reaches the tool's inputSchema.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
claimYesA factual claim ("The Earth's average temperature rose 1.1°C since 1880") or an article URL (https://example.com/article). URLs are auto-detected and the pipeline extracts claims from the page content.
compactNoIf true, strip the full evidence arrays and computed analytics from the response, leaving claims and claim maps. Smaller payload for agents that only need orientation.
max_tierNoMaximum tier to attempt — "lookup", "consensus", "quick" or "full" (default). A CEILING, not a floor: cached and consensus hits still return instantly at their own lower price, so the default costs ~£0.15 only for claims never researched before. Set "quick" to cap spend at ~£0.07, accepting web-search-only sourcing and heuristic classification (see _meta.limitations).full
max_age_hoursNoSkip cache hits older than this many hours. Stale lookup hits are discarded and the pipeline re-runs at the next tier up to max_tier. 0 means never serve a cached result.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses substantial behavioral detail: URL auto-detection, article mode with up to 5 auto-selected claims, tier fallback and pricing, the 10-minute deduplication guarantee, charge-on-executed-tier semantics, and output structure including _meta limitations. This is exactly the kind of context an agent needs to predict side effects and costs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections, front-loaded purpose, and every block earning its place: submission modes, tiers, charging/dedup rules, and output shape. Despite its length, it is dense with actionable information and avoids fluff.

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

Completeness5/5

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

For a complex multi-tier tool, the description is remarkably complete: it covers input modes, tier semantics, costs, caching behavior, output structure, and limitations via _meta. With a full input schema and output schema present, nothing essential is missing.

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 input schema already fully documents all four parameters with 100% coverage. The description adds beyond the schema by explaining tier fallback behavior, cost implications, and the ceiling semantics of max_tier, which sharpens an agent's understanding of how parameter choices affect execution and spend.

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

Purpose5/5

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

Description opens with a specific verb and resource: 'Evidence research for a factual claim or article URL.' It clearly distinguishes this check tool from the sibling result-retrieval tools by describing the research pipeline and output, leaving no doubt that tru8_check initiates analysis rather than fetching prior results.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives strong usage context: how to submit claims/URLs, how URL article mode works, the tier fallback order, and how max_tier controls spend. It does not explicitly contrast tru8_check with tru8_get_result or tru8_get_result_raw, but the operational guidance for when to use this tool and how to adjust tier behavior is clear.

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.

TDQS

A4.4/5.0
Disambiguation4/5

tru8_check is clearly the submission/analysis entry point, while tru8_get_result and tru8_get_result_raw both retrieve a previous check but are explicitly differentiated by whether computed analytics are included. The overlap is intentional and the descriptions make the choice clear.

Naming Consistency5/5

All tools share the tru8_ prefix and follow a consistent snake_case verb_noun pattern: check, get_result, get_result_raw. The raw suffix cleanly signals the variant without breaking the naming convention.

Tool Count5/5

Three tools is well-scoped for this service: one to submit an evidence check and two retrieval variants for different use cases. Each tool earns its place and there is no unnecessary bloat.

Completeness4/5

The core lifecycle of submitting a check and retrieving results is covered, including a raw option for custom processing. Minor gaps exist around discovering past checks or explicitly polling in-progress work, but the primary workflow has no dead ends.