Skip to main content
Glama
Sign In
mindreset-mcp

mindreset-mcp

by stvlynn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mindreset_simple_text

Send plain text to a MindReset device screen by providing a device ID and message; add an optional title.

Instructions

Send simple text content to MindReset device screen

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": {
      "deviceId": "<deviceId>",
      "message": "<message>"
    },
    "name": "mindreset_simple_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoText title
messageYesText content
deviceIdYesDevice serial number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It doesn't say whether the device must be online, whether this replaces or queues on screen content, whether display is transient or persistent, or what happens on failure. Only the mutation intent ('Send') is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with the action and target front-loaded and no wasted words. It is appropriately sized, though not unusually informative.

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?

For a device-mutating tool with no annotations and no output schema, the description leaves key agent questions unanswered: delivery requirements, content replacement behavior, and failure modes. The 100% schema coverage covers parameters but not behavior.

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 description coverage is 100%, so all three parameters (title, message, deviceId) are already documented in the schema. The description adds no format, length, or device-resolution detail beyond what the schema states, so the baseline 3 applies.

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?

States a specific verb ('Send') and resource ('simple text content') with the target ('MindReset device screen'). The word 'simple' implicitly distinguishes it from mindreset_complex_text and mindreset_text_with_icon, though it never names those siblings explicitly.

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 guidance on when to choose this over mindreset_text_with_icon, mindreset_complex_text, or mindreset_image. The word 'simple' implies a lightweight case but no conditions, prerequisites, or alternatives are stated.

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