Skip to main content
Glama
Sign In
AbleSign MCP

AbleSign MCP

by MartinLoeper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

add_screen_playlist_items

Add media files or web applications to a screen playlist. Specify the screen, items (1-50), and insertion position.

Instructions

Add 1-50 media-file or web-app items to a screen playlist.

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>",
      "items": "<items>"
    },
    "name": "add_screen_playlist_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
positionNoend
screen_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions item count and types and the position parameter implies ordering, but it does not disclose side effects (e.g., appending vs. replacing), validation behavior, or error conditions.

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?

The description is a single efficient sentence with no wasted words. However, it could be more informative without sacrificing conciseness given the complexity of the items parameter.

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?

Despite having an output schema, the description lacks sufficient detail to fully understand the behavior, especially for the items array which is loosely typed. It does not help the agent differentiate from sibling tools that also involve playlist items.

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

Parameters2/5

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

The input schema has 3 parameters with 0% description coverage. The description adds that items are 'media-file or web-app items' but does not explain the required fields within the objects (additionalProperties true). Screen_id and position are not described beyond schema defaults.

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 clearly states the verb 'Add', the resource 'items to a screen playlist', and specifies constraints (1-50, media-file or web-app). It distinguishes from sibling tools like save_screen_playlist and update_screen_playlist_item by implying batch addition.

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?

The description implies usage for adding multiple items at once but does not explicitly state when to use this tool versus alternatives (e.g., save_screen_playlist for full replacement) or provide when-not scenarios.

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