SiteGraph

fact_checks

Find published fact-check articles by query, language, and recency to verify claims and locate relevant sources.

Instructions

Search published fact-checks (Google Fact Check Tools API; needs GOOGLE_FACTCHECK_API_KEY).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "fact_checks"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes
`language`	No
`max_age_days`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 26, 2026

TDQS

C2.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the external Google Fact Check Tools API dependency and the required GOOGLE_FACTCHECK_API_KEY, which is important environment context. It does not state rate limits, failure behavior, or explicitly that the operation is read-only, though searching implies a read.

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 with the core action front-loaded. Every phrase contributes context about the resource, API, and credential requirement. It is terse rather than verbose, though the terseness leaves other gaps.

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

Completeness2/5

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

An output schema exists, so return-value structure need not be described. The description does mention the API dependency and API key requirement. However, for a three-parameter search tool with no schema descriptions and multiple sibling tools, it omits parameter semantics and usage differentiation, leaving the definition incomplete.

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

Parameters1/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 for all three parameters. It says nothing about the query, language, or max_age_days parameters beyond the bare schema titles. This leaves the agent without semantic guidance for filtering.

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 gives a specific verb and resource: search published fact-checks. It also identifies the backing API. It does not explicitly distinguish this query-search tool from siblings such as claimreview_from_url or the timeline tools.

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?

Usage is only implied by 'Search published fact-checks.' There is no guidance on when to use this instead of claimreview_from_url, claim_timeline, url_timeline, or image_provenance, and no exclusions are stated.

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

Deploy Server