Skip to main content
Glama

direct_upload_tns

Upload .tns files to TI-Nspire internal storage over USB with NavNet/DocLink, optionally packaging Python code first, eliminating the need for an external browser.

Instructions

Sube un archivo .tns directamente al almacenamiento interno de la calculadora TI-Nspire por USB mediante el protocolo de paquetes NavNet/DocLink (servicio 0x4060, Bulk Endpoints IN/OUT) sin depender de ningún navegador web externo.

:param filename: Nombre de destino del archivo (ej. 'solucionador.tns'). :param python_code: Código Python opcional para empaquetar al vuelo antes de subir. :param local_tns_path: Ruta local opcional a un archivo .tns ya existente en disco. :param remote_directory: Carpeta de destino en la memoria de la calculadora (por defecto '/PyLib').

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": {
      "filename": "<filename>"
    },
    "name": "direct_upload_tns"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
python_codeNo
local_tns_pathNo
remote_directoryNo/PyLib

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does valuable work by disclosing the transport mechanism (USB, NavNet/DocLink, endpoints) and that no browser is needed, but it omits operationally important behavior: whether an existing file at the destination is overwritten, what happens if the device is disconnected or the protocol handshake fails, and any permission/connection prerequisites.

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?

The structure is sensible: a front-loaded purpose sentence followed by one line per parameter, with no filler. The opening sentence is long and mixes purpose with low-level protocol trivia (service ID, endpoint types) that an agent rarely needs to choose or call the tool.

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 need not be described. However, for a device-mutating operation with zero annotations, the definition should say more about overwrite behavior, required connected state, and how the two source parameters interact; those omissions matter for calling it correctly.

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 description must compensate, and it does: each of the four parameters gets meaning — destination name, optional in-flight Python packaging, optional pre-existing local .tns path, and the device folder with its '/PyLib' default. The remaining gap is that it never states the relationship between python_code and local_tns_path (mutual exclusivity or precedence when both are supplied).

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 states a specific verb and resource ('Sube un archivo .tns directamente al almacenamiento interno de la calculadora TI-Nspire por USB') and adds differentiating mechanism detail (NavNet/DocLink packets, service 0x4060, bulk IN/OUT endpoints, no external web browser). That 'direct USB transport, no browser' framing clearly separates it from the conversion/creation siblings like convert_script_to_tns or create_python_tns_document.

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?

It gives a clear usage context — upload a ready-made or on-the-fly packaged .tns straight to the device over USB rather than going through a browser — which implies when an agent should reach for it. It stops short of explicit when-not conditions or naming an alternative tool, so an agent must still infer the boundary versus the conversion siblings.

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