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
`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

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behaviors. The description adds metered access and explains responseFormat backward compatibility, including tokenizer-measured context savings, providing valuable behavioral context beyond annotations without contradiction.

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?

Two concise, front-loaded sentences with no redundancy; each phrase contributes directly to understanding the tool's purpose, usage, and behavior.

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?

Given the output schema exists and annotations cover safety, the description covers usage context, response format choices, and the alternative tool, making it complete for an API brief compiler.

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 covers 100% of parameters with detailed descriptions. The description reinforces service requirement, clarifies endpoint's optional narrowing role, and explains responseFormat's compact vs full purpose, adding some semantic value beyond the schema.

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?

Description clearly states the tool compiles a single callable third-party API brief with explicit components (base URL, auth, params, body, response codes). It also distinguishes from the sibling factreason_api_schema by advising when to prefer that tool, ensuring clear differentiation.

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?

Explicitly states that service is required and endpoint optionally narrows the operation, and directly recommends factreason_api_schema for multiple endpoints, providing clear when-to-use and when-not-to-use guidance.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: schema lookup, auth playbook, integration brief, breaking changes, package advisory, deprecation scan, component lookup, key creation, payment link creation, discovery, and subscription creation. Descriptions include cross-references that explicitly disambiguate overlapping areas such as api_schema vs. integration_brief vs. auth_playbook.

Naming Consistency4/5

All tools share the factreason_ prefix and snake_case styling, which makes them predictable, but the naming mixes action verbs like create_key, discover_api, and subscribe_spec_changes with noun phrases like api_schema, auth_playbook, and integration_brief. This is mostly consistent but not a strict verb_noun convention across all tools.

Tool Count5/5

11 tools is well within the ideal range for a server with this scope. The count feels intentional: discovery, detail lookups, comparison, validation, key management, billing, and subscription monitoring each have a dedicated tool without unnecessary overlap.

Completeness4/5

The surface covers the main workflow well: discover an API, inspect schemas and auth details, build an integration brief, check version changes and deprecations, handle npm/PyPI packages, and subscribe to spec changes. Minor gaps include no tool to list or delete watches and no direct balance lookup, but these are workarounds.

Integration brief

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources