Skip to main content
Glama

Get install steps for a player

get_install_steps
Read-onlyIdempotent

Steps to install the Screenbird player on a device type, ending with the pairing code that the user enters in the dashboard.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "device": "<device>"
    },
    "name": "get_install_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceYesDevice to install the player on: signage_stick = Amazon Signage Stick, fire_tv = Fire TV Stick or Cube, android_tv = Android TV or Google TV, windows / macos / linux / raspberry_pi = computer, browser = test screen in a browser tab without installing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / device / description
      Added value: +"Device to install the player on: signage_stick = Amazon Signage Stick, fire_tv = Fire TV Stick or Cube, android_tv = Android TV or Google TV, windows / macos / linux / raspberry_pi = computer, browser = test screen in a browser tab without installing."
  2. 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 the operation read-only, idempotent, non-destructive, and closed-world. The description adds meaningful behavioral context by explaining that the result is a sequence of steps ending with a pairing code the user enters in the dashboard, which helps the agent relay instructions correctly.

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?

The description is a single front-loaded sentence with no wasted words. It conveys purpose and the important terminal output (pairing code) efficiently.

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 one-parameter retrieval tool with rich enum documentation and no output schema, the description is nearly complete. It explains what the result contains and how it ends, though it could say a bit more about the installation workflow context.

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 device parameter has 100% schema description coverage, including detailed enum meanings such as browser being a test screen without installation. The description only refers to 'device type' and adds no further parameter semantics, so the schema carries the burden.

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 clearly states the specific resource (install steps for the Screenbird player) and the key input dimension (device type), plus the notable output ending with a pairing code. It does not explicitly distinguish itself from siblings, but no sibling obviously overlaps with installation instructions.

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: call this when a user needs installation instructions for a particular device. There is no explicit when-to-use versus alternatives such as search_help, no prerequisites, and no exclusions.

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