Skip to main content
Glama

Maple Minute

Get prices

get_prices
Read-onlyIdempotent

Prices in CAD: government fees and our fees, separately. No API key needed.

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_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds genuinely useful behavior beyond them: the response is denominated in CAD, splits government fees from company fees, and requires no authentication — all of which affect how an agent presents results. It stops short of saying whether prices are live or cached and omits any rate-limit context.

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?

Two short, front-loaded sentences with no filler; the return composition comes first and the access note last. The only soft spot is the ambiguous pronoun 'our fees', which leaves the agent to guess the owning entity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining the return value, and it only partially does so: it discloses currency and the two fee buckets but not the shape (per-service list, addon-level, flat totals) or the data's freshness. For a zero-parameter pricing endpoint this is adequate but leaves real gaps.

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 no parameters at all, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool is a 4. The brief mention of currency and fee categories is redundant with the schema's emptiness but harmless.

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 names the resource (prices) and, unusually, specifies the return composition — government fees and company fees listed separately — plus the currency (CAD). It does not use an explicit verb or contrast itself with siblings such as get_payment_link, but an agent can still tell what this tool fetches.

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

Usage Guidelines2/5

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

There is no statement of when to call this tool, no prerequisites, and no pointer to alternatives for pricing-adjacent tasks like get_payment_link or add_addon. The 'No API key needed' line is an access caveat, not usage guidance, so the agent must infer the trigger condition entirely.

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