Skip to main content
Glama
Sign In
terminus-mcp

terminus-mcp

by gjermundgaraba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get display context

get_display_context
Read-onlyIdempotent

Retrieve a redacted Terminus device, its rendering model, and current playlist. Supply a device_id if the server manages multiple devices.

Instructions

Get a redacted Terminus device, its rendering model, and current playlist. Provide device_id when the server has multiple devices.

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

Input Schema

NameRequiredDescriptionDefault
device_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds behavioral context by noting the returned data is 'redacted' and specifying exactly what is returned (device, rendering model, playlist), which goes beyond the structured fields.

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 two sentences long, front-loaded with the main action and resource, followed by a conditional usage note. Every word earns its place with no redundancy.

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

Completeness5/5

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

Despite no output schema, the description explains the return contents (redacted device, rendering model, current playlist) and the only parameter condition. Given the low complexity (one optional parameter) and good annotations, the description is fully sufficient for an agent to select and invoke the tool.

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?

Schema description coverage is 0%, so the description must compensate. It does so by explaining when to provide the optional device_id ('when the server has multiple devices'), adding meaningful semantics beyond the integer schema with no description.

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 retrieves a redacted Terminus device, its rendering model, and current playlist. The verb 'Get' plus the specific resource and associated data distinguishes it from sibling tools focused on screens, playlists, and docs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear conditional guidance: 'Provide device_id when the server has multiple devices.' It does not explicitly name alternatives or exclusions, but the context is sufficient for a single-purpose tool.

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