Skip to main content
Glama

What Toronto Walk costs

get_pricing
Read-only

The game is free; lists the optional one-time purchases with their prices in Canadian dollars. Read-only: nothing can be bought through this server.

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
languageNoLanguage of names and descriptions: en (English, default) or zh (Simplified Chinese).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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; the description reinforces this and adds two genuinely new facts: the base game is free, and no purchase transaction is possible through the server, which pre-empts a wrong action. It stops short of describing pagination or response shape, but for a static price list that is minor.

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 clauses, front-loaded with the free-to-play fact and then the capability, then the read-only constraint. No filler, no restated name.

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 one-optional-parameter read-only lookup with no output schema, the description covers what the tool returns, the currency, and the safety boundary. Only the return structure (e.g., a list of named items) is left implicit, which is a small gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter (language, enum en/zh) is fully documented in the schema at 100% coverage, so the schema carries the load. The description adds only the CAD currency, a meaningful detail for the returned prices but nothing about the language parameter.

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?

Specific verb+resource: "lists the optional one-time purchases with their prices in Canadian dollars" tells an agent exactly what comes back. It does not name or contrast with siblings (get_game_info, list_places), but those are clearly different domains, so mis-selection risk is low.

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

Usage Guidelines3/5

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

Usage is implied rather than stated — an agent can infer this is the tool for pricing questions. The "nothing can be bought through this server" clause steers away from a purchase attempt, but there is no explicit when-to-use versus get_game_info, which is the plausible neighboring question.

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