Skip to main content
Glama

About Toronto Walk

get_game_info
Read-only

What Toronto Walk is, the link to play, which devices and languages it supports, how to start and the controls. 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": "get_game_info"
  }
}

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

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, so the trailing 'Read-only' adds nothing. What does add value is the disclosure of what the tool returns (link, device/language support, start instructions, controls), which matters since there is no output schema. It stops short of describing response format or whether the play link points to an external site.

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?

A single compact sentence that front-loads the subject and lists the returned content with no filler. The only structural weakness is that it reads as a fragment rather than a complete statement of what the tool does.

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 simple, parameterless-by-default read tool with no output schema, the description covers the essential question of what information comes back. Only the shape/format of the response is left unstated, which is a minor gap given the tool's low complexity.

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 the single language parameter has a documented enum with a stated default, so the schema carries this dimension. The description's phrase 'languages it supports' refers to returned content rather than the language parameter, so it adds no parameter-level meaning. Baseline 3 is appropriate.

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 enumerates exactly what the tool surfaces about Toronto Walk: the game's description, play link, supported devices and languages, how to start, and controls. That content inventory distinguishes it from get_pricing and list_places. It loses a point only because it is a noun phrase with no explicit verb such as 'returns' or '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 when-to-use statement, no mention of the sibling tools (get_pricing, list_places), and no conditions or exclusions. An agent must infer that this is the general 'about the game' lookup purely from the content list.

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