Skip to main content
Glama

Places to find in Toronto Walk

list_places
Read-only

Every place and experience the in-game album counts (Union Station, the PATH, subway stations, streets and landmarks), each with a short description. Read-only.

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": "list_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoplace = somewhere you walk to; experience = something you do (ride the subway, take a taxi); all (default) = both.
languageNoLanguage of names and descriptions: en (English, default) or zh (Simplified Chinese).
undergroundNotrue = only places below street level (PATH, subway, train concourses); false = only street level; leave out for both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the trailing 'Read-only.' merely restates that rather than adding value. What the description does add is meaningful scope information: it covers the complete set of album-counted items and each entry carries a short description. It is silent on return shape, ordering, and whether the list is paginated or fixed in size.

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 sentences, front-loaded with the resource scope and supported by a tight parenthetical example list. The only waste is the trailing 'Read-only.', which duplicates the readOnlyHint annotation instead of earning its place.

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 some burden for describing return values; it only says entries have 'a short description', leaving the agent to guess the fields returned (name, kind, location, etc.). For a zero-required-parameter listing tool with fully documented optional filters this is adequate, but the return shape should be stated explicitly.

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?

Schema description coverage is 100% and both enums are documented with defaults and semantics (e.g. 'all (default) = both', 'en (English, default)'), so the schema fully carries parameter meaning. The description adds nothing beyond that, which is the expected baseline when the schema does the heavy lifting.

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?

States the resource precisely — every place and experience the in-game album counts — and grounds it with concrete examples (Union Station, the PATH, subway stations, streets, landmarks). The verb is carried by the tool name rather than the description, and it doesn't explicitly contrast with get_game_info or get_pricing, so it falls short of a 5.

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?

The description explains what the tool contains but never says when to call it versus get_game_info or get_pricing, nor when not to call it. It also gives no prerequisite context (e.g. whether it must be called in-game or works with adverse conditions), so the agent must infer usage purely from the content scope.

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