Only Fake Facts

List invented sources

list_sources

Read-onlyIdempotent

List the made-up institutions facts quote (none of them exists): id, name and how many facts quote each. Pass an id as search_facts' source to get those facts.

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

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the facts (machine-translated from English, labels included). Defaults to the request's Accept-Language, else English.

Output Schema

Name	Required	Description
`lang`	No
`note`	No
`site`	No
`sources`	Yes
`disclaimer`	Yes	Every fact is false.
`schema_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "disclaimer": {
+      "description": "Every fact is false.",
+      "type": "string"
+    },
+    "lang": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "schema_version": {
+      "type": "integer"
+    },
+    "site": {
+      "type": "string"
+    },
+    "sources": {
+      "items": {
+        "properties": {
+          "count": {
+            "type": "integer"
+          },
+          "fabricated": {
+            "const": true
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "url": {
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "disclaimer",
+    "sources"
+  ],
+  "type": "object"
+}

AddedNov 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context — that the institutions are fictional and that the listing includes per-source fact counts — but says nothing about ordering, pagination, or result size.

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?

Two short sentences, front-loaded with the resource and the caveat that the data is fabricated, followed by the action link. Slightly awkward phrasing around 'facts quote' costs a point but nothing is redundant.

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, annotations covering the safety profile, and full schema description coverage, the description only needs purpose plus non-obvious caveats — and it delivers both (fictional data, id reuse in search_facts). Nothing essential 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 the single optional lang parameter is fully documented in the schema, including its enum and Accept-Language default. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

Names a specific verb (List) and resource (made-up institutions) and enumerates the returned fields — id, name, and fact count — which lets an agent distinguish this from fact-level siblings like get_fact and search_facts. It stops short of contrasting with trace_sources, the closest ambiguous sibling, so it is not a full 5.

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?

Explicitly states the follow-up workflow: pass a returned id as search_facts' source parameter. That gives clear context for why and when to call this tool, but there are no stated exclusions or comparison against trace_sources/list_topics.

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

All Only Fake Facts 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.

Resources

Need Help?