FactGrid (Renamed to FactReason)

Integration brief

factreason_integration_brief

Read-onlyIdempotent

Compile one callable third-party API brief: base URL, auth scheme, required parameters and types, request body, and documented response codes. Service is required and endpoint optionally narrows the operation. Set responseFormat="compact" for tokenizer-measured context savings; the backward-compatible default returns the full brief plus compact form. Uses metered access. Prefer factreason_api_schema when exploring multiple endpoints.

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" or "Twilio"
`endpoint`	No	Optional path or operation fragment used to select one call
`responseFormat`	No	Use compact for the callable facts only; full preserves the legacy brief response	full

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`brief`	No
`found`	No
`billed`	No
`compact`	No
`message`	No
`service`	No
`tokenMetrics`	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 17, 2026

addedInput schema / properties / responseFormat

Added value: +{
+  "default": "full",
+  "description": "Use compact for the callable facts only; full preserves the legacy brief response",
+  "enum": [
+    "full",
+    "compact"
+  ],
+  "type": "string"
+}

removedOutput schema / properties / compact / additionalProperties
```
Removed value: -true
```
changedOutput schema / properties / compact / type
```
Previous value: -"object"New value: +"string"
```

addedOutput schema / properties / tokenMetrics

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "compactTokens": {
+      "type": "number"
+    },
+    "encoding": {
+      "const": "o200k_base",
+      "type": "string"
+    },
+    "fullTokens": {
+      "type": "number"
+    },
+    "reductionPct": {
+      "type": "number"
+    },
+    "savedTokens": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed6 schema fields changedAug 14, 2026

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

changedInput schema / properties / endpoint / description

Previous value: -"Optional: narrow to endpoints matching this path or operation, e.g. \"payment_intents\", \"messages\""New value: +"Optional path or operation fragment used to select one call"

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

changedInput schema / properties / service / description

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

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

changedOutput schema / (root)

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

AddedAug 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds value beyond them: 'Uses metered access' discloses a cost/quota trait, and it clarifies the responseFormat default behavior ('backward-compatible default returns the full brief plus compact form'), which the schema does not spell out.

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?

Front-loaded with purpose in the first sentence, followed by parameter guidance, format behavior, metered access, and the sibling alternative. Dense but each sentence earns its place; minor redundancy in restating the responseFormat tradeoff that the schema also gestures at.

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?

An output schema exists, so return values need not be explained, and the description still summarizes the brief's contents. Metered access, the required/narrowing parameter roles, and the sibling alternative are all covered, leaving nothing an agent needs to call correctly unstated.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3, but the description adds real meaning: it notes service is required, endpoint optionally narrows the operation, and explains responseFormat='compact' delivers 'tokenizer-measured context savings' while the default returns the full brief plus compact form. This goes beyond the schema's terse enum descriptions.

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 (Compile) and resource (one callable third-party API brief), then enumerates exactly what the brief contains: base URL, auth scheme, required parameters and types, request body, and documented response codes. It also explicitly names the sibling factreason_api_schema as the alternative, so an agent can distinguish the two 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 Guidelines4/5

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

Provides clear context (service required, endpoint narrows the operation) and an explicit alternative with its selecting condition: 'Prefer factreason_api_schema when exploring multiple endpoints.' It lacks explicit when-not conditions or prerequisites beyond this, so it stops short of a 5.

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.