Skip to main content
Glama

Get Cost Estimate

get_cost_estimate
Read-onlyIdempotent

[Meta · free] Preview what a tool call will cost before running it. Pass tool_name plus the params you intend to call it with: variable-cost tools (get_post_set_engagers, map_constellation, enrich_people, linkedin_profile_posts, linkedin_company_posts, linkedin_post_reactions, linkedin_post_comments, run_stream_now) are priced from those params with the same formula the tool's balance pre-check uses. Returns { tool_name, cost_max, cost_typical?, unit, explanation, cost (= cost_max), balance, sufficient, known_tool }. cost_max is the worst case the balance must cover; cost_typical is what such a call usually costs (you are charged only for what is actually fetched). Also accepts a stream type (external_profile, company, topic, person_interests, hiring_signals, ad_watch) to preview its per-page run price (stream_cost). Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tool_name": "<tool_name>"
    },
    "name": "get_cost_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNoThe params you plan to call the tool with. Examples: get_post_set_engagers { profile_id | collection_id | post_ids / post_urls, max_posts, max_pages_per_post, max_enrich, freshness_days } (with a scope it counts the posts that actually need a sync); map_constellation { max_targets }; enrich_people { person_ids, linkedin_urls, max_credits }; linkedin_profile_posts / linkedin_company_posts { max_posts }; linkedin_post_reactions / linkedin_post_comments { max_pages }; run_stream_now { stream_id, max_pages }.
tool_nameYesMCP tool name (e.g. 'get_post_set_engagers') or stream type (e.g. 'external_profile')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / params / description
      Previous value: -"The params you plan to call the tool with. Examples: get_post_set_engagers { profile_id | collection_id, max_posts, max_pages_per_post, max_enrich, freshness_days } (with a scope it counts the posts that actually need a sync); map_constellation { max_targets }; enrich_people { person_ids, linkedin_urls, max_credits }; linkedin_profile_posts / linkedin_company_posts { max_posts }; linkedin_post_reactions / linkedin_post_comments { max_pages }; run_stream_now { stream_id, max_pages }."New value: +"The params you plan to call the tool with. Examples: get_post_set_engagers { profile_id | collection_id | post_ids / post_urls, max_posts, max_pages_per_post, max_enrich, freshness_days } (with a scope it counts the posts that actually need a sync); map_constellation { max_targets }; enrich_people { person_ids, linkedin_urls, max_credits }; linkedin_profile_posts / linkedin_company_posts { max_posts }; linkedin_post_reactions / linkedin_post_comments { max_pages }; run_stream_now { stream_id, max_pages }."
  2. Changed2 schema fields changed
    • changedInput schema / properties / params / description
      Previous value: -"Optional call params. For map_constellation pass { max_targets } to get its worst-case cost (1 + 3 × max_targets; default 5). For enrich_people pass { person_ids, linkedin_urls, max_credits } to get 3 × people (capped by max_credits)."New value: +"The params you plan to call the tool with. Examples: get_post_set_engagers { profile_id | collection_id, max_posts, max_pages_per_post, max_enrich, freshness_days } (with a scope it counts the posts that actually need a sync); map_constellation { max_targets }; enrich_people { person_ids, linkedin_urls, max_credits }; linkedin_profile_posts / linkedin_company_posts { max_posts }; linkedin_post_reactions / linkedin_post_comments { max_pages }; run_stream_now { stream_id, max_pages }."
    • changedInput schema / properties / tool_name / description
      Previous value: -"MCP tool name (e.g. 'get_posts') or stream type (e.g. 'external_profile')"New value: +"MCP tool name (e.g. 'get_post_set_engagers') or stream type (e.g. 'external_profile')"
  3. Changed1 schema field changed
    • changedInput schema / properties / params / description
      Previous value: -"Optional call params. For map_constellation pass { max_targets } to get its worst-case cost (1 + 3 × max_targets; default 5)."New value: +"Optional call params. For map_constellation pass { max_targets } to get its worst-case cost (1 + 3 × max_targets; default 5). For enrich_people pass { person_ids, linkedin_urls, max_credits } to get 3 × people (capped by max_credits)."
  4. Changed1 schema field changed
    • changedInput schema / properties / params / description
      Previous value: -"Reserved for future per-call estimation"New value: +"Optional call params. For map_constellation pass { max_targets } to get its worst-case cost (1 + 3 × max_targets; default 5)."
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the bar is lower; the description still adds real value by disclosing cost_max as worst case, cost_typical as the usual charge, that billing reflects only what is actually fetched, and that the formula matches the tool's balance pre-check. This goes well beyond the annotation set.

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-loaded with the purpose and the [Meta · free] tag, then usage, then return shape. Dense but every clause earns its place, including the enumerated tool names and stream types, which are load-bearing for correct invocation.

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?

No output schema exists, yet the description enumerates every returned field (tool_name, cost_max, cost_typical, unit, explanation, balance, sufficient, known_tool) and explains their meaning. Combined with the two-mode usage guidance, nothing an agent needs is 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 baseline is 3, but the description adds meaning: params is a pass-through of the intended call's arguments used solely for pricing, and tool_name additionally accepts stream type values. The schema's params examples carry most of the per-tool detail, keeping this just below top marks.

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: "Preview what a tool call will cost before running it." It also names the two modes of operation (variable-cost tools priced from params, or a stream type for per-page run price), which makes it distinguishable from siblings like get_credit_balance.

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 a clear when-to-use condition (before running a call) and enumerates exactly which tools are variable-cost and thus worth previewing. It stops short of explicitly contrasting with get_credit_balance or stating when a preview can be skipped, so it is strong context without full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources