TaskFuel.ai

Discover paid APIs

discover

Read-onlyIdempotent

Find a paid endpoint for a capability you lack: image, video, music or speech generation, transcription, email finding and verification, people and company enrichment, social and market data, travel, OCR, translation, sending email, phone calls or letters. 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. Read an endpoint's full docs before its first call: a search hit is a one-line summary, required parameters and their allowed values are only in the docs, and a guessed value the endpoint accepts is charged at that value's price. 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

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.5/5.0

Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing cost semantics (catalog search is free; a guessed value the endpoint accepts is billed at that value's price) and negative-result semantics ('no results is a real answer'). It does not mention result caps, pagination, or how many hits a query returns, which is the remaining behavioral gap.

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, then cost, then the argument recipes — a sensible order with no filler sentences. The capability enumeration is long but arguably load-bearing for a discovery tool; the colon-and-dash stacking makes it denser than it needs to be.

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 no output schema, the description carries the return-format burden and largely meets it: a search hit is a one-line summary, while `url`+`method` yields full docs including parameter schema. Minor omission is what a domain listing or empty-argument response actually contains.

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; the description earns an extra point by explaining the combination rules the schema cannot express — that `url` and `method` must be supplied together and what that pair yields (parameters, request-body schema), and that all-empty arguments returns the allowed service 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?

States a specific verb and resource ('Find a paid endpoint for a capability you lack') and enumerates the capability space so an agent knows the coverage boundary immediately. It is clearly distinguishable from siblings like `call`, `quote`, and `balance`, which operate on endpoints already known.

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 routes between the three calling modes: `query` for keyword search ('the fastest path from a task to an endpoint'), `domain` to list one service's endpoints, `url`+`method` for full docs, and no arguments for allowed domains. It also imposes a sequencing rule — read full docs before the first call — with the reason (search hits are one-line summaries).

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?