Skip to main content
Glama

get_pricing

Read-onlyIdempotent

Read current account-plan prices for permitted data sources and estimate request_count query costs per source; free and does not spend Credits. Downloads return per-TB rates.

Instructions

Read current account-plan prices for permitted MCP data sources and estimate the cost of request_count calls per source. For youtube_download returns the per-TB byte rate, not a per-request estimate; request_count does not apply to downloads. Counts queries, not search results; each page or batch item is a separate query. Free; does not reserve or spend Credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoAuthorized source to price. Omit for all sources permitted by this API Key.
request_countNoNumber of calls to estimate, not the number of search results. Does not apply to per-TB downloads.
response_formatNoAgent-readable presentation. MCP defaults to Markdown; json returns the original JSON text, text returns indented fields. Structured fields remain available. Does not change billing or the stored job.markdown

Output Schema

NameRequiredDescriptionDefault
codeNoMachine-readable error code when the operation fails.
noteNoEstimation limitations.
planNoCurrent account plan.
unitNo
detailNoAdditional problem detail returned by the API.
pricesNoCurrent rates for sources permitted by this API Key.
messageNoError, delivery, or continuation instructions.
request_idNoFlashData request identifier for support and tracing.
http_statusNoUpstream HTTP status, when an upstream request was made.
requestCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description still adds real value beyond that: it is free, spends no Credits, and explains that request_count counts queries (each page or batch item separately) rather than search results.

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?

Four tight sentences, each carrying distinct information: what it reads, the download exception, the query-counting rule, and the cost model. The purpose statement is front-loaded and nothing is padded, though the sentence order scatters related caveats rather than grouping them.

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?

With an output schema present and full parameter documentation, the description only needs to cover pricing semantics, which it does: free, no Credit spend, per-TB for downloads, and per-query counting. An agent has everything needed to call it and interpret the result correctly.

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, and the description goes slightly beyond it by restating the download exception and adding the counting nuance that each page or batch item is a separate query. It does not, however, add anything about the source enum or response_format that the schema does not already say.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: read account-plan prices per source and estimate cost for a given request_count. That is unambiguous, but it never contrasts itself with siblings like get_balance or get_usage, so an agent must infer that pricing lookup differs from balance/usage retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: 'Free; does not reserve or spend Credits' tells the agent this is a safe pre-flight estimate, and the youtube_download caveat marks an exception. However, there is no explicit instruction such as when to call this versus get_balance or get_usage, so the agent is left to infer the routing.

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