terminus-mcp

Search screen documentation

search_screen_docs

Read-onlyIdempotent

Search Terminus and TRMNL screen docs, guides, components, and examples. Omit query to get recommended starting points.

Instructions

Find the Terminus authoring guide, official TRMNL screen docs, Framework components, and examples. Omit query for the recommended entry points.

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

Input Schema

Name	Required	Description	Default
`query`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already convey read-only, idempotent, non-destructive behavior. The description adds useful context about search scope and the omit-query behavior for entry points, going beyond annotations without contradicting them.

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?

Two sentences, front-loaded with the core purpose, no redundancy. Every clause adds value, making it a model of concise writing.

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?

For a simple search tool with one optional parameter and no output schema, the description covers what it searches, how to invoke without query, and leans on annotations for safety profile. Complete and sufficient.

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 has one parameter (query) with no description, so the description must compensate. 'Omit query for the recommended entry points' clarifies that query is optional and implicitly defines it as search terms. This is helpful but could be more explicit about query's semantics.

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 finds documentation (Terminus authoring guide, TRMNL screen docs, Framework components, examples) with a specific verb 'Find' and resource. It distinguishes from siblings like read_screen_doc by emphasizing a search over docs rather than reading a specific one.

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?

Provides clear context for usage, notably omitting query to get recommended entry points. Does not explicitly mention alternatives or exclusion scenarios, but the context makes the primary use case evident.

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

Deploy Server