FactGrid (Renamed to FactReason)

Discover an API

factreason_discover_api

Read-onlyIdempotent

Find third-party APIs for a capability when the provider is unknown. Supply a concise capability such as "sms" or "manage DNS"; returns ranked services, example endpoints, and a next step. Uses metered access. When the provider is already known, call factreason_integration_brief instead.

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.
`capability`	Yes	Capability to search for, e.g. "send an SMS" or "charge a card"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`count`	No
`found`	No
`billed`	No
`message`	No
`results`	No
`nextStep`	No
`capability`	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 / capability / description

Previous value: -"What you need to do, e.g. \"send an SMS\", \"charge a card\", \"upload a file\""New value: +"Capability to search for, e.g. \"send an SMS\" or \"charge a card\""

addedInput schema / properties / capability / minLength
```
Added value: +2
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "billed": {
+      "type": "boolean"
+    },
+    "capability": {
+      "type": "string"
+    },
+    "count": {
+      "type": "number"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "hint": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "nextStep": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedAug 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a trait annotations do not: "Uses metered access", a cost/billing consequence the agent should know before calling. It stops short of describing rate limits or quota behavior, so it is strong but not exhaustive.

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?

Three short sentences, front-loaded with the purpose and the unknown-provider condition, then the return shape, then the routing alternative. Every sentence carries distinct information with no filler.

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?

Output schema exists, so the brief mention of ranked services and a next step is enough without enumerating return fields, and annotations cover safety. With metered access disclosed and the sibling routing rule stated, nothing an agent needs to call this 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%, so both parameters (including the apiKey header fallback and the capability examples) are already documented in the schema, which sets the baseline at 3. The description's guidance to "Supply a concise capability such as 'sms' or 'manage DNS'" is a mild hint about expected granularity but largely overlaps the schema's own examples.

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 ("Find third-party APIs") plus the narrowing condition "when the provider is unknown", which separates it cleanly from the provider-known path. An agent can distinguish it from factreason_integration_brief without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit selection rule: use this when the provider is unknown, and names the concrete alternative (factreason_integration_brief) for the known-provider case. Nothing about when to route here versus there is left to inference.

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.