Skip to main content
Glama
Sign In

Galatic.ai

by ai.galatic
OverviewDiscussionsAdmin

Model pricing

get_model_pricing
Read-onlyIdempotent

Get what each generation model costs. Without modelId returns { prices }, optionally filtered by category (for example "image" or "video"); with modelId returns { price } for that model (404 if unknown) and category is ignored. Each price has modelId, category, unit, description, credits (charged per unit) and retailPrice in US dollars at the Creator plan's rate per credit (null when the model has no credit cost). Read-only; use before an expensive generation to quote the cost.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "get_model_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
modelIdNoOne model, e.g. "flux-pro". category is ignored when set.
categoryNoFilter for the full list, e.g. "image" or "video".
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Filter for the full list, e.g. \"image\" or \"video\"."
    • addedInput schema / properties / modelId / description
      Added value: +"One model, e.g. \"flux-pro\". category is ignored when set."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The readOnly and idempotent hints are already covered by the annotations, but the description adds real behavioral information beyond them: a 404 for unknown modelId, that category is ignored when modelId is set, and that retailPrice is computed at the Creator plan's per-credit rate and may be null. It does not discuss result size or whether the full list is ever paginated, which is a minor omission.

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?

It is dense and front-loaded: the two modes and the return shapes come first, followed by field semantics, and the usage note comes last. It is longer than strictly necessary; the per-field enumeration partly repeats the schema, but no sentence is wasted.

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?

Given no output schema, the description fully specifies both return shapes ({ prices } versus { price }), the fields within a price, the unit of retailPrice, and the 404 outcome. An agent can call this correctly and interpret the result without further information.

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 the meaning of the return fields (modelId, category, unit, description, credits, retailPrice) and spells out the precedence between modelId and category. The modal behavior of modelId and category is partly duplicated from the schema, so the description does not add much more.

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 description opens with a specific verb and resource ("Get what each generation model costs") and immediately makes clear that this is a pricing lookup, not a catalogue lookup, so it differs from the sibling list_models. Both modes (list and single-model) are stated up front.

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?

"Use before an expensive generation to quote the cost" gives a clear trigger and contextualizes when to call it. It does not, however, name an alternative or an exclusion; for example, it never contrasts itself with list_models or get_billing_overview, so the routing guidance is implied rather than explicit.

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

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