Skip to main content
Glama
Sign In
mindreset-mcp

mindreset-mcp

by stvlynn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mindreset_text_with_icon

Send text content with an icon and optional tap link to a MindReset device screen by providing a device ID and message.

Instructions

Send text content with icon and optional link 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_text_with_icon"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoBase64 encoded PNG icon data (40px*40px)
linkNoHTTP/HTTPS link or Scheme URL for tap-to-jump
titleNoText title
messageYesText content
deviceIdYesDevice serial number
signatureNoText signature

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 says 'Send' and targets a device screen, but omits whether it replaces existing content, what permissions are required, rate limits, or whether the device must be online.

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 front-loaded sentence with no wasted words. It is efficient and earns its place, though it is terse for a six-parameter tool.

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?

This is a send tool with six parameters, no annotations, and no output schema. The description omits return behavior, prerequisites, and side effects, leaving the agent without enough context to invoke it correctly in all cases.

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 coverage is 100%, so the schema documents all six parameters including icon, link, title, message, deviceId, and signature. The description mentions icon, optional link, and text content but adds no format or constraint details beyond what the schema already provides, making 3 the correct baseline.

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 the verb 'Send' and the resource 'text content with icon and optional link' to 'MindReset device screen.' It distinguishes itself from mindreset_image and simple_text by including icon/link, but does not explicitly name or compare against siblings, so a 4 is appropriate.

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?

Provides no when-to-use guidance or alternative selection criteria. The implied context is sending rich text with an icon, but nothing tells the agent when to choose this over mindreset_simple_text or mindreset_complex_text.

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