Skip to main content
Glama

aiworker-data

by org.duckdns.aiworker

claim_check

Extract checkable factual claims from buyer-submitted text or a public URL, and verdict each one — supported, contradicted, unsupported or unverifiable — against Wikipedia and any buyer-supplied source URLs, with verbatim quoted evidence and links. Informational only. Price $0.05 per call, paid with USDC over x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoa public https url whose page is fetched and checked instead of text
textNobuyer text to check, at most 8 000 characters; exactly one of text or url is required
sourcesNoup to 5 https urls the model may cite as evidence, in addition to Wikipedia
max_claimsNomaximum claims to extract and verdict; default 5

Schema Changelog

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

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the transparency burden. It discloses that the tool is informational only, mentions the price and payment method, and describes what evidence sources are used and what output is produced.

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 a single compact sentence that conveys purpose, output, constraints, and pricing without excessive verbosity. Slight density from including pricing and payment details inline is acceptable and does not harm clarity.

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?

Since there is no output schema, the description adequately explains what the tool will return: verdicts, quoted evidence, and links. It also clarifies the evidence scope (Wikipedia plus up to 5 buyer-supplied URLs), making the tool's behavior sufficiently understandable in context.

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 schema covers all four parameters with 100% coverage. The description adds meaningful semantic context beyond the schema, such as requiring exactly one of text or url, the default max_claims of 5, and the role of sources as additional evidence alongside Wikipedia.

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: extract checkable factual claims from text or URL and verdict each claim against Wikipedia and buyer-supplied sources. It also specifies the output includes verdicts, quoted evidence, and links.

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 use for fact-checking claims, but does not explicitly distinguish when to use this tool versus sibling tools like scrape_markdown or scrape_summary. It gives no direct when-to-use/when-not-to-use guidance beyond the core purpose.

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

All aiworker-data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

The set splits into three clear domains, but within scraping and yields there are tiered duplicates: scrape_markdown/scrape_summary and defi_yields/yield_report overlap in output, with the latter being supersets. Descriptions clarify the differences, but an agent could still pick the wrong tier.

Naming Consistency4/5

All tools use lowercase snake_case with descriptive, domain-prefixed names, so the convention is predictable. The only inconsistency is that scrape_* tools are verb-led while defi_* and yield_report are noun phrases, but this is a minor stylistic deviation.

Tool Count5/5

Six tools is a reasonable, well-scoped set for a paid data-access server, covering fact-checking, DeFi data, and web scraping without bloat. The tiered duplicates add some redundancy but each has a distinct price/output level.

Completeness4/5

For the three apparent subdomains, the core workflows are covered: claims are checkable, DeFi protocols and yields are queryable, and pages can be scraped with or without summarization. Minor gaps exist, such as no DefiLlama protocol search by name and no batch/multi-URL operations, but agents can work around these.

Resources