Skip to main content
Glama
Sign In
AbleSign MCP

AbleSign MCP

by MartinLoeper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_screen_group_members

Replace a screen group's membership by specifying up to 100 screen IDs. Update the list of screens assigned to a group in one operation.

Instructions

Replace a screen group's membership with up to 100 screen IDs.

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": {
      "group_id": "<group_id>",
      "screen_ids": "<screen_ids>"
    },
    "name": "set_screen_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes
screen_idsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/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 discloses that the tool replaces (overwrites) the membership and enforces a limit of 100 screen IDs. However, it does not mention side effects, error conditions, or transactionality.

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?

One sentence clearly conveys the purpose and a key constraint. No extraneous information. Front-loaded and efficient.

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?

Given the tool has an output schema (not shown) and only two simple parameters, the description covers the essential behavior. It lacks mention of prerequisites or validation, but is nearly complete for this use case.

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 0%, so the description must add meaning. It implies group_id identifies the group and screen_ids are the new member IDs, with a cap of 100. This adds marginal value over the schema's type-only definitions.

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 action (replace), the resource (screen group's membership), and a constraint (up to 100 screen IDs). It distinguishes the tool from siblings like get_screen_group_members (read) and add_screen_group_playlist_items (different operation).

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 the tool is for fully replacing membership, but it does not explicitly state when to use it versus alternatives like adding/removing members. No prerequisites or context for when not to use it.

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