AbleSign MCP

list_screens

Retrieve a list of digital signage screens filtered by orientation, online status, tags, and other criteria to manage your display network efficiently.

Instructions

List screens. Comma-separate orientation, online-status, or tag filters.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`title`	No
`offset`	No
`sort_by`	No
`screen_tags`	No
`orientations`	No
`online_status`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations provided, so description must disclose behaviors. It only mentions listing and filters; lacks details on pagination, sorting, or that it's a read-only operation. Insufficient for an unannotated tool.

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?

Single sentence is concise, but lacks structure and completeness. Every word earns its place, but more information could be included without excessive length.

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 7 parameters and no annotations, the description is too minimal. It covers filtering but omits pagination (limit/offset) and sorting behavior. Output schema exists but does not compensate for missing behavioral context.

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?

Schema coverage is 0%, and description adds meaning for three parameters (orientations, online_status, screen_tags) by explaining they accept comma-separated values. However, limit, title, offset, and sort_by remain unexplained.

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?

Description states it lists screens and mentions comma-separated orientation, online-status, or tag filters. This clearly identifies the tool's purpose and distinguishes it from siblings like list_screen_groups.

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 explicit guidance on when to use this tool versus alternatives (e.g., get_screen for a single screen). Description only hints at filter options but does not provide context or exclusions.

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

Deploy Server