Skip to main content
Glama
Sign In
ti-nspire-mcp

ti-nspire-mcp

by reliasdomi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sync_esp32_remote_screen

Synchronizes TI-Nspire CX II screen capture and bidirectional commands with an ESP32 over WebSockets or serial to enable remote screen viewing on iPhone.

Instructions

Sincroniza en tiempo real la captura de pantalla de la TI-Nspire CX II y comandos bidireccionales con la placa ESP32 para el modo "Pantalla Remota desde iPhone" (WebSockets / Serial).

:param status_text: Texto de estado a mostrar en el visor remoto de iPhone. :param command: Comando o evento de tecla opcional a transmitir de forma bidireccional.

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

Input Schema

NameRequiredDescriptionDefault
commandNo
status_textNoTI-Nspire CX II Live

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It does disclose the transport (WebSockets / Serial) and that the sync is bidirectional and real-time, but it says nothing about whether the call blocks, opens/persists a connection, needs a paired device, what error conditions look like, or what side effects occur on the ESP32 or calculator.

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?

One front-loaded purpose sentence followed by two compact parameter lines; no filler. Minor inefficiency from docstring-style formatting rather than a stated contract, but it stays short and readable.

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

Completeness3/5

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

An output schema exists, so return values needn't be explained. However, for a live-hardware bidirectional sync tool with no annotations and 0% param coverage, the definition leaves out operational essentials such as connection prerequisites, blocking behavior, and failure modes.

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 0%, so the description must compensate. The :param lines do add meaning beyond the bare titles — status_text is the text shown in the iPhone remote viewer, command is an optional key/event transmitted bidirectionally — but they don't specify format, validation, allowed values, or what happens when command is null.

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 and resource: real-time synchronization of the TI-Nspire CX II screen capture and bidirectional commands with the ESP32 board, scoped to 'Pantalla Remota desde iPhone' mode over WebSockets/Serial. It does not differentiate itself from related siblings such as capture_screen_live or generate_esp32_firmware, so an agent cannot tell from the description alone which one to pick.

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?

There is no when-to-use or when-not-to-use guidance, no stated prerequisites (e.g. ESP32 must be paired/connected), and no named alternative. The mode name hints at context but the agent must infer the selection criteria.

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