Skip to main content
Glama
factreason

factreason

Official
by factreason
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

factreason_discover_api

Read-onlyIdempotent

Find third-party APIs for a capability when you don't know the provider. Supply a concise capability like 'send SMS' to get ranked services, example endpoints, and a next step.

Instructions

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
NameRequiredDescriptionDefault
capabilityYesCapability to search for, e.g. "send an SMS" or "charge a card"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
countNo
foundNo
billedNo
messageNo
resultsNo
nextStepNo
capabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.2
    • 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\""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"
+}
  2. First observedv2.0.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful context beyond these: metered access (a cost/billing signal) and that it returns ranked services, example endpoints, and a next step. It clearly communicates the operation's outcome and cost implications, adding non-obvious behavioral traits.

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?

The description is two sentences with zero filler. It front-loads the core verb and resource, followed by concrete examples and an explicit sibling redirect. Every clause earns its place, making it efficient for an AI agent to parse.

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 tool's low complexity (1 param), full schema coverage, and rich output schema, the description covers all necessary context: what it does, when to use it, when not to, what it returns, and a caveat (metered access). No additional information is needed for correct invocation.

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% and has a single parameter with a clear example description. The description adds extra value by giving more examples ('sms', 'manage DNS') and emphasizing the need for conciseness. This goes slightly beyond the schema's example, enhancing semantic understanding without excessive duplication.

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's purpose: finding third-party APIs for a capability when the provider is unknown. It uses a specific verb ('Find'), specifies the resource ('third-party APIs'), and includes scope ('when the provider is unknown'). Also explicitly distinguishes from a sibling ('call factreason_integration_brief instead').

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?

Provides explicit use-case context ('when provider is unknown') and gives a direct alternative ('when the provider is already known, call factreason_integration_brief instead'). Also supplies input format examples ('sms', 'manage DNS') and a next-step hint ('returns ... a next step'). This is model guidance.

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

Deploy Server

Other Tools