FactReason

Deprecation scan

factreason_deprecation_scan

Read-onlyIdempotent

Scan publisher specifications for deprecated endpoints or parameters, sunset dates, and replacement operations. Omit filters for the catalogue-wide view, pass service to limit one API, and add endpoints to check selected paths. Uses metered access when findings exist. Use factreason_api_breaking_changes for broader version-to-version changes.

Input Schema

TableJSON Schema

Name	Required	Description
`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`	No	Optional service filter, e.g. "Stripe" or "Twilio"
`endpoints`	No	Optional endpoint paths to check within the selected service

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`found`	No
`message`	No
`results`	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"
+}

Changed7 schema fields changedAug 14, 2026

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

changedInput schema / properties / endpoints / description

Previous value: -"Optional list of endpoint paths to check, e.g. [\"v1/charges\", \"v1/customers\"]"New value: +"Optional endpoint paths to check within the selected service"

addedInput schema / properties / endpoints / items / minLength
```
Added value: +1
```
addedInput schema / properties / endpoints / minItems
```
Added value: +1
```

changedInput schema / properties / service / description

Previous value: -"Optional: filter by service name, e.g. \"Stripe\", \"Twilio\""New value: +"Optional service filter, e.g. \"Stripe\" or \"Twilio\""

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

changedOutput schema / (root)

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

First observedAug 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds a real behavioral trait not in the annotations — 'Uses metered access when findings exist' — which tells the agent about cost incurred on results. It does not add return-format or rate-limit detail, but the output schema covers returns, so a 4 is warranted.

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 tight sentences: purpose first, then scoping mechanics, then the metering note and the routing pointer to the sibling. No filler and no repetition of what the schema or annotations already state.

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 0 required params, 100% schema coverage, full annotations, and an output schema, the remaining burden on the description is usage and cost context — both supplied. An agent has everything needed to decide when to call this versus factreason_api_breaking_changes and how to scope the call.

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 coverage is 100%, so the baseline is 3, but the description adds semantics the schema lacks: what happens when the optional filters are omitted (catalogue-wide) and how service and endpoints compose (endpoint paths are checked within the selected service). That default/combination behavior is genuinely beyond the per-field schema text.

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 (scan) and resource (publisher specifications) plus the exact artifacts it surfaces: deprecated endpoints/parameters, sunset dates, and replacement operations. It explicitly names the sibling it is not (factreason_api_breaking_changes), so an agent can route correctly 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 concrete invocation guidance — omit filters for the catalogue-wide view, pass service to scope to one API, add endpoints to check specific paths — and names the alternative tool with the condition that selects it ('broader version-to-version changes'). This is explicit when-to-use, how-to-scope, and when-to-use-something-else.

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

All 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.