Skip to main content
Glama
Sign In
AbleSign MCP

AbleSign MCP

by MartinLoeper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_screen_playlist

Retrieve a screen's playlist and settings to view its current content schedule and configuration.

Instructions

Get a screen's playlist and settings.

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": {
      "screen_id": "<screen_id>"
    },
    "name": "get_screen_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
screen_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are present, so the description must convey behavioral traits. It implies a read operation ('Get'), but does not disclose authorization needs, rate limits, or whether the call is idempotent. The description adds minimal value beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one sentence) and front-loaded, but it sacrifices necessary detail. While brevity is valued, the description lacks sufficient information to be fully useful, earning an average score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description does not need to detail return values. However, it omits context about the relationship to siblings and the scope of 'playlist and settings'. For a tool with a single parameter, the description should be more complete to guide the agent.

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

Parameters1/5

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

With 0% schema description coverage and only one parameter (screen_id), the description does not explain what the parameter represents or how to obtain it. The schema provides a title and type, but no further context. The description completely fails to compensate for the lack of schema documentation.

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 action ('Get') and the resource ('a screen's playlist and settings'). It differentiates from sibling tools like 'get_screen' (which likely returns screen metadata) and 'get_screen_group_playlist' (for groups). The verb and resource are specific, but no further distinction is made.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'get_screen', 'save_screen_playlist'). The description does not mention prerequisites, limitations, or scenarios where this tool should be chosen over siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools