Skip to main content
Glama

TaskFuel.ai

by ai.taskfuel.app
OverviewDiscussionsAdmin

Call a paid API

call

Call one of the discovered endpoints and pay for it from the user's balance. This is the only tool here that spends anything. quote the same request first to read the real price off the endpoint's HTTP-402 challenge, then repeat it here with max_amount_usd set to that quote — always send it, so a repriced endpoint cannot charge more than the price you read. Calls above $10 are refused; max_amount_usd can tighten that ceiling further. (dry_run: true still works and is identical to quote.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesendpoint URL, exactly as `discover` returned it
bodyNorequest body, sent as JSON: pass the object itself, e.g. {"prompt": "a cat"}, not a JSON-encoded string
modelNoyour own model id, e.g. claude-opus-5. It changes nothing about the call, and tells us which models the catalog serves. Skip it if you are not sure.
methodNoHTTP method (default GET)
dry_runNoquote the real price without paying, same as `quote`
headersNoextra request headers, no auth headers needed
max_amount_usdNoyour spend ceiling for this call, in USD. Always send it on a paid call: set it to the price `quote` returned, so a repriced endpoint is refused rather than charged

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / dry_run / description
      Previous value: -"quote the real price without paying"New value: +"quote the real price without paying, same as `quote`"
    • changedInput schema / properties / max_amount_usd / description
      Previous value: -"your own spend ceiling for this call, in USD"New value: +"your spend ceiling for this call, in USD. Always send it on a paid call: set it to the price `quote` returned, so a repriced endpoint is refused rather than charged"
  2. Changed1 schema field changed
    • addedInput schema / properties / model
      Added value: +{
+  "description": "your own model id, e.g. claude-opus-5. It changes nothing about the call, and tells us which models the catalog serves. Skip it if you are not sure.",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / body / description
      Previous value: -"request body, sent as JSON — pass the object itself, e.g. {\"prompt\": \"a cat\"}, not a JSON-encoded string"New value: +"request body, sent as JSON: pass the object itself, e.g. {\"prompt\": \"a cat\"}, not a JSON-encoded string"
    • changedInput schema / properties / headers / description
      Previous value: -"extra request headers — no auth headers needed"New value: +"extra request headers, no auth headers needed"
  4. Changed2 schema fields changed
    • 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"
-}
    • changedInput schema / required
      Previous value: -[
-  "url",
-  "context"
-]New value: +[
+  "url"
+]
  5. Changed2 schema fields changed
    • 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"
+}
    • changedInput schema / required
      Previous value: -[
-  "url"
-]New value: +[
+  "url",
+  "context"
+]
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false; the description adds the material behavior: this is the only tool that spends money, spending is drawn from the user's balance, a $10 hard refusal limit, and the anti-repricing guarantee from max_amount_usd. That is exactly the context annotations cannot convey.

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?

Front-loads the spending identity, then sequences the quote-then-call workflow, then the limits. No sentence is redundant and the parenthetical on dry_run removes a real ambiguity rather than padding.

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?

Given openWorldHint, no output schema, and nested request bodies, the description covers cost, safety, and invocation well. It leaves one genuine gap: it never says how the result is retrieved or that get_result is the sibling for that, and it is silent on async versus synchronous completion.

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 real meaning on top: max_amount_usd should be set to the quote's price, model changes nothing about the call, and dry_run duplicates quote. It does not add detail on method/headers beyond what the schema already says.

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 (call) and resource (discovered endpoints) and immediately scopes it as the only spending tool, which cleanly separates it from quote, discover, and balance. An agent can identify its role without opening any 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 an explicit ordering contract: quote first to read the HTTP-402 price, then repeat here with max_amount_usd set to that quote. It also states the hard ceiling ($10), that dry_run is equivalent to quote, and why max_amount_usd must always be sent (repricing protection).

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

All TaskFuel.ai toolsInspect
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