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

ti-nspire-mcp

by reliasdomi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_multipage_tns_document

Create multi-page .tns documents combining spreadsheets, LaTeX notes, Python, Lua, calculator, and Ndless content for TI-Nspire CX II.

Instructions

Genera un documento .tns avanzado con soporte multipágina y multiaplicación: hojas de cálculo ('spreadsheet'), notas matemáticas formateadas con LaTeX ('notes'), scripts de Python ('python'), scripts de Lua ('lua'), calculadoras CAS ('calculator') y binarios nativos de Ndless ('ndless').

:param filename: Nombre del archivo .tns a crear. :param pages: Lista de especificaciones de página (TNSPageSpec: page_type, title, content, formulas_latex, spreadsheet_columns). :param document_title: Título global del documento. :param output_directory: Directorio donde guardar el archivo .tns.

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>",
      "pages": "<pages>"
    },
    "name": "create_multipage_tns_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYes
filenameYes
document_titleNoTI-Nspire MultiApp Document
output_directoryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/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, yet it only says what gets generated. It does not disclose whether an existing file at the same path is overwritten, whether the document is uploaded to a connected calculator or written locally, what errors can occur for invalid page specs, or whether the operation is reversible.

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

Conciseness5/5

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

The definition is front-loaded with the capability and supported formats, then lists each parameter compactly in a docstring style. Every line contributes information, with no filler or repetition of the tool name.

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 no explanation, and the parameter documentation is reasonably thorough for a 4-parameter tool. Still, for a file-creating mutation with zero annotations, the absence of any note on overwrite behavior, write location, or failure modes leaves a meaningful gap.

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% and the pages array is typed only as a generic object, so the ':param' lines do real work by naming the nested fields (page_type, title, content, formulas_latex, spreadsheet_columns) and by enumerating valid page_type values in the opening paragraph. Only output_directory and document_title lack detail beyond their names and defaults.

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?

The description opens with a specific verb and resource ('Genera un documento .tns avanzado con soporte multipágina y multiaplicación') and enumerates the supported page types (spreadsheet, notes, python, lua, calculator, ndless). This clearly separates it from single-format siblings, but it never names those siblings to make the distinction explicit.

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: the multipage/multiapp framing suggests this is the tool for composite documents rather than single-format ones, which is implicitly useful against create_python_tns_document or create_lua_or_ndless_tns. However, there is no explicit when-to-use statement, no exclusions, and no mention of prerequisites such as an active device connection.

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