Skip to main content
Glama

ExducerAI GPU cloud

List prices

get_pricing
Read-onlyIdempotent

List prices in CAD: GPU-hour per GPU model, object storage per GB-month, and the Models API. Use this instead of any remembered price.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds meaningful context beyond them: the currency unit (CAD) and the fact that returned figures are authoritative rather than memorized. It does not discuss pagination or price-update cadence, which keeps it below a 5.

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?

Two short sentences, the resource and its covered price dimensions front-loaded, with the usage directive last. Every clause carries information; nothing is redundant with the schema or annotations.

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?

For a zero-parameter read-only tool this is close to complete: it names the currency and the three price categories, which implicitly sketches the return structure even without an output schema. A brief note on how prices are keyed or formatted is the only minor gap.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning to explain. The description correctly spends its words on scope and currency instead of parameter detail.

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?

Specific verb+resource ("List prices") with the exact scope spelled out: GPU-hour per GPU model, object storage per GB-month, and the Models API, plus the currency (CAD). This clearly separates it from the deployment/invoice/usage listing siblings, which do not return prices.

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 this instead of any remembered price" is an explicit when-to-use directive that tells the agent to prefer this tool over cached or assumed figures. It stops short of naming a when-not condition or a concrete alternative tool, but no sibling appears to overlap in purpose.

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