Flat Earth Science

Tested claims

find_claims

Read-onlyIdempotent

Searches the website's tested claims and flat-earth investigations, or returns one by id. Each result gives the claim, the verdict, the key evidence and the link to its page; an empty query lists all of them.

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

Input Schema

Name	Required	Description	Default
`id`	No	Exact claim id returned by an earlier search, for the full claim, verdict and evidence.
`query`	No	Words to look for in a claim's title, topic or summary, such as moon landing or horizon. Empty lists every claim.

Output Schema

Name	Required	Description	Default
`item`	No
`view`	Yes
`items`	No
`query`	No
`total`	No
`request`	Yes
`pageSize`	No
`nextCursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description is free to add what matters: the shape of each result (claim, verdict, key evidence, page link) and the fact that an empty query returns the full list. It does not discuss pagination or result-count limits, which is the main remaining gap.

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?

Two tight sentences, with the two modes front-loaded and the return contents and empty-query rule following in priority order. No filler or redundant restatement of the title.

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?

With an output schema present, the description needn't document return structure in detail, and it still summarizes the fields an agent can expect. Combined with rich annotations and fully documented parameters, nothing required to call this tool correctly is missing.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters already carry full descriptions, including the empty-query behavior and the maxLength bounds. The description restates rather than extends those semantics, so the baseline of 3 applies.

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?

States a specific verb and resource ('searches the website's tested claims and flat-earth investigations') and covers both operating modes: query search and single-record retrieval by id. The sibling tools are geometric calculators, so the domain distinction is immediate and no agent would confuse the two.

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?

Usage is implied rather than stated: it notes that an empty query lists everything, which implicitly tells the agent how to enumerate the catalog, and the id path is described as needing an id from an earlier search. There is no explicit 'use this when…' framing or named alternative, so guidance is adequate but thin.

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

All Flat Earth Science tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.