Skip to main content
Glama

QR Wall plans and prices

get_pricing
Read-only

Every QR Wall plan (Free, Premium, Professional) and one-off add-on, with prices in USD, what each includes and its limits, the education & nonprofit Professional offer, plus the cheapest way to cover a single event.

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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds that this is a static plan catalog with USD-denominated prices and limit details. It does not mention whether prices are current or how the data is structured, and with no output schema the return shape is only loosely described.

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?

One front-loaded sentence that opens with the resource ('Every QR Wall plan') and then lists coverage items; every clause maps to content the caller would get. The enumeration is dense but purposeful, with no filler or repetition.

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 static lookup with no output schema, the description covers what the response contains (plans, prices, inclusions, limits, discounts, single-event option) well enough to call confidently. The only gap is freshness/authority of pricing data, which is minor for this tool type.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly signals a parameterless full-catalog fetch rather than suggesting any filtering is possible.

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 resource with full scope: all QR Wall plans (Free, Premium, Professional), one-off add-ons, USD prices, inclusions and limits, plus the education/nonprofit offer and single-event coverage. An agent can tell this is a pricing/catalog lookup rather than a search or comparison tool.

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?

Usage is clearly implied by enumerating the questions it answers (plan pricing, limits, nonprofit discount, cheapest single-event option), which routes several intents to this one tool. It stops short of naming a sibling (e.g. compare) or stating exclusions, so the 'when not to use' half is absent.

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