Skip to main content
Glama

convert_latex_to_nspire_xml

Convert LaTeX math expressions into TI-Nspire XML tags and native symbolic notation, with optional evaluation marking for calculator use.

Instructions

Convierte expresiones matemáticas en LaTeX a etiquetas XML matemáticas nativas de TI-Nspire () y a notación simbólica interna de TI-Nspire OS.

:param latex_expression: Expresión en LaTeX (ej. '\frac{-b \pm \sqrt{b^{2}-4ac}}{2a}'). :param evaluate: Si es True, marca la etiqueta para evaluación automática.

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": {
      "latex_expression": "<latex_expression>"
    },
    "name": "convert_latex_to_nspire_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
evaluateNo
latex_expressionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/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 does disclose the output shape, namely <expr> tags plus internal symbolic notation, and it explains that evaluate marks the tag with eval="1" for automatic evaluation, which is useful context. However, it says nothing about whether the operation is pure, whether it can fail on unsupported LaTeX constructs, or what error behavior to expect.

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 conversion purpose comes first, followed by compact per-parameter notes, so an agent can skim it. The :param formatting is a little terse for prose, but every line conveys real information and there is no filler.

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?

This is a simple 2-parameter, single-purpose transformation, and an output schema exists, so the description does not need to spell out return values. It covers both inputs and the output form well. It is only short of full completeness because it never addresses failure modes or how the result feeds into the TNS document tools.

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 has to document both parameters, and it does: latex_expression is described along with a concrete LaTeX example, and evaluate is described with the exact effect it has on the emitted XML attribute. The only gap is that neither the accepted LaTeX subset nor the type-level constraint of the string parameter is 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?

The description gives a specific verb and resource: it converts LaTeX math expressions into TI-Nspire native XML math tags (<expr>) and into TI-Nspire OS internal symbolic notation. That is far more precise than restating the name. It does not say how it relates to siblings such as convert_script_to_tns, which is why it is not 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 Guidelines2/5

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

The description never says when to use this tool or when to use another one instead; it does not identify inputs it does not handle, and it does not explain how it combines with the document-building siblings. The only usage signal is the implied context that it is a conversion step, which the agent has to infer.

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