Skip to main content
Glama

Explain how PadConsole works

explain_how_it_works
Read-onlyIdempotent

Use this when someone asks how to start, what equipment or devices are needed (TV, laptop, phones, camera), or how friends in different homes can play together. Returns the steps and the link to open.

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

Input Schema

NameRequiredDescriptionDefault
topicNostart (default), remote (friends in different homes) or devices (what hardware is needed).
localeNoLanguage the user is writing in: tr (Turkish), de (German), es (Spanish), id (Indonesian), pt (Portuguese), ru (Russian), ar (Arabic) or en (everything else). Default en.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / locale / description
      Previous value: -"Language the user is writing in: tr (Turkish), de (German), es (Spanish), id (Indonesian) or en (everything else). Default en."New value: +"Language the user is writing in: tr (Turkish), de (German), es (Spanish), id (Indonesian), pt (Portuguese), ru (Russian), ar (Arabic) or en (everything else). Default en."
    • changedInput schema / properties / locale / enum
      Previous value: -[
      -  "tr",
      -  "en",
      -  "de",
      -  "es",
      -  "id"
      -]New value: +[
      +  "tr",
      +  "en",
      +  "de",
      +  "es",
      +  "id",
      +  "pt",
      +  "ru",
      +  "ar"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / locale / description
      Previous value: -"Language the user is writing in: tr (Turkish), de (German) or en (everything else). Default en."New value: +"Language the user is writing in: tr (Turkish), de (German), es (Spanish), id (Indonesian) or en (everything else). Default en."
    • changedInput schema / properties / locale / enum
      Previous value: -[
      -  "tr",
      -  "en",
      -  "de"
      -]New value: +[
      +  "tr",
      +  "en",
      +  "de",
      +  "es",
      +  "id"
      +]
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds that the response is a static set of steps plus a link, which is mildly useful context but largely restates what the output schema supplies. No additional behavioral detail such as static-versus-dynamic content or locale fallback behavior is disclosed.

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 trigger condition and followed by the return contract. Nothing is wasted, though the phrasing is dense enough that the topic-to-question mapping requires a second read.

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, no-required-parameter read tool with a full output schema and fully documented enums, the description covers purpose, triggers, and return shape adequately. The only gap is guidance on how it relates to the game-focused siblings when a question is ambiguous.

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 coverage is 100% and both parameters carry enum descriptions that already explain 'start/remote/devices' and the locale codes. The description's hardware example (TV, laptop, phones, camera) loosely corresponds to the 'devices' topic but adds no mapping, defaults, or interaction detail beyond the schema. Baseline 3 is appropriate.

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?

The description names a specific resource — how PadConsole works, covering setup steps, required hardware (TV, laptop, phones, camera), and multi-home play — and states what is returned (steps plus the link to open). It is clearly distinct from the sibling tools, which all deal with games rather than product onboarding.

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?

The opening 'Use this when someone asks...' clause gives concrete invocation triggers that map onto the three topics. It stops short of naming alternatives or exclusions (for example, deferring game-specific questions to get_game_details or recommend_games), so routing between siblings is only implied by domain difference.

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