TaskFuel.ai

Discover paid APIs

discover

Read-onlyIdempotent

Find a paid endpoint. Free: searching the catalog costs nothing. Keyword search is the fastest path from a task to an endpoint: pass query. No results is a real answer: nothing offers that term. Pass domain to list one service's endpoints, url + method together for one endpoint's full docs (parameters, request-body schema), or no arguments at all for the allowed service domains.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	an endpoint URL. With `method`, returns its full docs
`query`	No	keywords to search every service's endpoints
`domain`	No	restrict to one service domain, e.g. 2s.io
`method`	No	HTTP method, required alongside `url`

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 18, 2026

changedInput schema / properties / url / description

Previous value: -"an endpoint URL — with `method`, returns its full docs"New value: +"an endpoint URL. With `method`, returns its full docs"

Changed2 schema fields changedAug 7, 2026

removedInput schema / properties / context

Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}

removedInput schema / required
```
Removed value: -[
-  "context"
-]
```

Changed2 schema fields changedAug 5, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "context"
+]
```

First observedJul 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real value beyond them: searching is free ('costs nothing', relevant in a paid-API context) and 'no results is a real answer' preempts the agent retrying an empty search.

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 the purpose, then cost, then the mode/parameter mapping; nearly every clause carries routing information. The 'No results is a real answer: nothing offers that term' sentence is slightly conversational but earns its place by setting expectations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 0 required parameters, no output schema, and flat params, the description covers everything needed to call it correctly, including what the url+method mode returns ('full docs (parameters, request-body schema)'). Return-format detail is light but adequate given no output schema exists.

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 goes further by specifying parameter combinatorics the schema does not: `url` + `method` must be passed together, `domain` alone lists a service's endpoints, and zero arguments returns the allowed domains.

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?

Opens with a specific verb+resource ('Find a paid endpoint') and immediately enumerates the four distinct lookup modes, which makes it clearly distinct from siblings like quote, call, and balance. An agent can identify the tool's role without opening the 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?

Gives concrete routing guidance for each argument combination ('pass `query`' for keyword search, `domain` for one service, `url` + `method` together for one endpoint's docs, no arguments for the domain list) and frames query as 'the fastest path from a task to an endpoint'. It does not explicitly name sibling tools or state when-not to use it, keeping it 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 TaskFuel.ai tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?