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

ti-nspire-mcp

by reliasdomi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

capture_screen_live

Captures the live TI-Nspire screen as RGB565 pixels, converts them to PNG, and returns Base64 data for visual analysis; optionally saves the image to disk.

Instructions

Envía el paquete NavNet de solicitud de captura de framebuffer (0x4024 / 0x4021) a la TI-Nspire, recibe los píxeles en formato RGB565 (16 bits, 320x240), los convierte con Pillow a PNG y los devuelve codificados en Base64 para análisis visual por la IA.

:param save_path: Ruta opcional en disco donde guardar también el archivo .png.

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

Input Schema

NameRequiredDescriptionDefault
save_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses the underlying protocol packets, pixel format, conversion step, and output encoding. However, it omits operational behavior such as the requirement that a device be connected, timeout/error conditions, and what happens if the capture fails. Solid process disclosure but incomplete runtime context.

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?

Front-loaded with the end-to-end pipeline in two compact sentences, then a reST-style param line. The protocol opcodes are mildly technical but earn their place by identifying the exact capture mechanism; little is wasted.

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

Completeness4/5

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

For a one-parameter tool with an output schema, the description covers input, processing, and output encoding thoroughly. The remaining gap is prerequisites for live hardware capture (connection state, failure handling), which an agent would benefit from knowing before invoking.

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 ':param save_path:' line does real work, explaining that it is an optional on-disk path to additionally persist the .png. The single parameter is fully clarified, though format expectations for the path are not specified.

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 chain: sends a NavNet framebuffer-capture request to the TI-Nspire, receives RGB565 320x240 pixels, converts to PNG, and returns Base64. An agent understands exactly what the tool produces. It does not explicitly differentiate itself from the related sibling sync_esp32_remote_screen, which keeps it short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied by the phrase 'para análisis visual por la IA', which signals the intended purpose but gives no explicit when-to-use or when-not-to-use criteria. Nothing tells the agent when to prefer this over sibling capture or sync tools.

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