Skip to main content
Glama

AnyAPI

by com.getanyapi.api
OverviewDiscussionsAdmin

Quote a price

quote_api
Read-only

Get the exact input-aware execution price for an API, free and without a key. Nothing is charged or executed. sku_id and input identify the proposed execution; pricing resolves exactly as it does for execution, and input validation can return invalid_input without a charge. Returns maxCostUsd (the ceiling reserved), minCostUsd (the likely charge), and the base/per-item breakdown explaining why they differ. These are USD amounts for this one call, not per-1,000-request catalog comparison rates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesthe exact normalized input payload being priced; the quote resolves pricing the same way execution does
sku_idYesthe API SKU slug to price
contextYesBrief purpose of this tool call within the requested task, used for analytics and user-intent tracking.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
exactYestrue when the price is exact (minCostUsd == maxCostUsd): a flat SKU or a sealed page
baseUsdYesfixed cost per call in USD, charged regardless of count
pricingYesa one-line human explanation of how this call is priced
maxCostUsdYesthe most this call can charge - the reserve held before running
minCostUsdYesthe likely charge - the cheapest route serves first
perItemUsdYesmarginal cost in USD per billable unit (see perItemUnit); 0 for a flat SKU
perItemUnitNothe unit perItemUsd is charged per: 'result' (default) or an input unit like 'username' for input-priced SKUs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"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.\""New value: +"Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking."
  2. Changed1 schema field changed
    • changedInput schema / properties / input / description
      Previous value: -"the exact input payload you plan to pass to run_api; the quote resolves pricing the same way the run will"New value: +"the exact normalized input payload being priced; the quote resolves pricing the same way execution does"
  3. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • 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: -[
-  "sku_id",
-  "input"
-]New value: +[
+  "sku_id",
+  "input",
+  "context"
+]
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnly, non-destructive); the description adds that quoting is free and keyless, that nothing is executed or charged, that input validation can return invalid_input at no cost, and that maxCostUsd is a reserved ceiling versus minCostUsd the likely charge. That is material behavioral context beyond the structured hints.

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 core promise (exact input-aware price, free, no key) before any detail, and the closing sentence usefully disambiguates the USD units. It is dense with a few overlapping clauses ('Nothing is charged or executed' vs. 'without a charge'), costing a little tightness.

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?

An output schema exists and annotations cover safety, yet the description still explains the two headline return fields and why they differ, and flags the invalid_input failure mode. Nothing an agent needs to call this tool correctly appears to be missing.

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 nonetheless adds real meaning: sku_id and input together identify the proposed execution and pricing resolves identically to execution, which tells the agent the input must match the payload it intends to run rather than being a loose query.

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?

The first sentence states a specific verb (get) and resource (execution price for an API) plus key modifiers (input-aware, free, no key). It implicitly separates itself from run_api by stating 'Nothing is charged or executed', so an agent can tell pricing apart from execution without opening either 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?

The description makes clear this is a non-charging preview of what execution would cost, which establishes when to reach for it. It does not explicitly name an alternative such as run_api or state an exclusion ('do not use this to actually execute'), so there is clear context but no routing rule.

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

All AnyAPI toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources