terminus-mcp

List screens

list_screens

Read-onlyIdempotent

Find rendered Terminus screens by filtering with a model ID or text in the screen name or label for targeted discovery.

Instructions

List rendered Terminus screens. Optionally filter by model or by text in the screen name or label.

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
`query`	No
`model_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that it lists 'rendered' screens, which is a mild behavioral nuance, but does not disclose details like return format, pagination, or ordering. This is sufficient but not rich.

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 unnecessary words. It efficiently states the action, resource, and optional filters, making it highly concise and well-structured.

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 list tool with two optional parameters and robust annotations, the description provides enough context to invoke correctly. It explains what is listed and the filtering options. It lacks return format details, but no output schema exists and the tool name implies a list of screens, so the gap is minor.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates by explaining that filtering can be done 'by model or by text in the screen name or label.' This maps loosely to the model_id and query parameters, giving meaning beyond the raw schema. However, it doesn't specify exact parameter-to-field mapping, so it's not perfect.

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 tool lists 'rendered Terminus screens' with optional filters, using specific verb 'List' and resource 'screens'. It distinguishes from siblings like list_playlists and search_screen_docs by focusing on screens rather than playlists or documentation.

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 listing screens with optional filters but does not explicitly state when to use this tool versus alternatives like search_screen_docs. No exclusions or alternative guidance is provided, so it's adequate but minimal.

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

Deploy Server