Skip to main content
Glama

tru8_check

Submit a claim or article URL to receive source-traced evidence research with element-level verification and tiered analysis from lookup to full investigation.

Instructions

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) — 30+ sources, LLM classification, coverage recovery

Charges based on tier actually executed, not tier requested. 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

Args: claim: A 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. max_tier: Maximum tier to attempt — "lookup", "consensus", "quick" (default), or "full". max_age_hours: Skip cache hits older than this many hours. If set, lookup hits that are stale will be discarded and the pipeline re-runs at the next tier up to max_tier. compact: If True, strip full evidence arrays from response (smaller payload).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
claimYes
max_tierNoquick
max_age_hoursNo
compactNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: auto-detection of URLs, tier fallback with costs and timing, caching behavior (max_age_hours), and output structure. It is transparent about what happens during execution without needing annotations.

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 well-structured with sections for tiers and output, and it is front-loaded with the purpose. It is slightly verbose due to detailed tier and output explanations, but every sentence adds value; minor redundancy is acceptable for clarity.

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?

Given the tool's complexity, lack of annotations, and 0% schema coverage, the description covers all necessary aspects: input, behavior, parameters, output structure (including nested objects), and execution details. It is fully complete without relying on the output schema.

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

Parameters5/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 compensate. It thoroughly explains each parameter: claim (text or URL, auto-detection), max_tier (options and default), max_age_hours (purpose), and compact (stripping evidence arrays). This adds significant meaning beyond the bare schema.

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?

The description clearly states the tool's purpose as evidence research for a factual claim or article URL, using a specific verb and resource. It distinguishes itself from sibling tools (tru8_get_result, tru8_get_result_raw) which are for retrieving results, thus avoiding ambiguity.

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 explains when to use the tool (for claims or URLs), details the tier system and fallback order, and mentions max_tier for cost control. It provides clear context but does not explicitly state when not to use it or list alternative tools, though the sibling differentiation is implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SamYatesSmith/tru8-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server