FactGrid (Renamed to FactReason)

Auth and error playbook

factreason_auth_playbook

Read-onlyIdempotent

Get publisher-declared authentication schemes, scopes, rate-limit headers, and error codes for one third-party API. Returns a structured playbook or nearest service suggestions, and marks undocumented details as unstated rather than guessing. Uses metered access. Prefer factreason_integration_brief when assembling a complete API call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`apiKey`	No	Your FactReason API key, from factreason_create_key. Pass it here when your MCP client cannot set the Authorization: Bearer header on this connection; if the header is set, omit this. Never pass a key that belongs to someone else.
`service`	Yes	Third-party API service, e.g. "Stripe", "Twilio", or "Cloudflare"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`found`	No
`compact`	No
`message`	No
`playbook`	No
`nearestServices`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

addedInput schema / properties / apiKey

Added value: +{
+  "description": "Your FactReason API key, from factreason_create_key. Pass it here when your MCP client cannot set the Authorization: Bearer header on this connection; if the header is set, omit this. Never pass a key that belongs to someone else.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

Changed4 schema fields changedAug 14, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / service / description

Previous value: -"Service name, e.g. \"Stripe\", \"Twilio\", \"Cloudflare\""New value: +"Third-party API service, e.g. \"Stripe\", \"Twilio\", or \"Cloudflare\""

addedInput schema / properties / service / minLength
```
Added value: +1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "compact": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "nearestServices": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "playbook": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

AddedAug 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds real value beyond them by disclosing metered access (cost), fallback behavior ('nearest service suggestions'), and the honesty trait of marking undocumented details 'unstated rather than guessing'. It does not state rate-limit or latency behavior for the tool itself, keeping it out of the 5 band.

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?

Three front-loaded sentences with no filler: purpose first, then fallback/honesty behavior, then the sibling routing. Efficient, though the return-behavior and routing clauses could be tightened slightly.

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?

For a 2-parameter read-only tool with an output schema and full schema description coverage, the description covers purpose, auth key mechanics indirectly, metered cost, fallback behavior, and sibling routing. Nothing an agent needs to call it 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 description coverage is 100%: the apiKey parameter's header-vs-key guidance and the service example are fully documented in the schema. The description adds no parameter-level syntax or format detail beyond what the schema already provides, 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 (get) and a concrete resource set (publisher-declared auth schemes, scopes, rate-limit headers, error codes) scoped to 'one third-party API'. It also differentiates itself by naming the sibling factreason_integration_brief and the distinct job it does.

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 routes the agent: 'Prefer factreason_integration_brief when assembling a complete API call,' giving a clear alternative and the condition that selects it. It lacks an explicit when-not statement (e.g., what to use when the service is unknown or when no playbook exists), so it falls short of the top band.

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

All FactGrid (Renamed to FactReason) tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.