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

ti-nspire-mcp

by reliasdomi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_calculator_status

Check the USB connection status of a Texas Instruments calculator on your computer and detect connected models such as TI-Nspire CX II, TI-Nspire CX, or TI-84 Plus CE before running other operations.

Instructions

Verifica el estado de conexión USB de la calculadora Texas Instruments en el ordenador. Detecta modelos como TI-Nspire CX II, TI-Nspire CX, TI-84 Plus CE, etc.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/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 disclosure burden. It makes the read-only, non-mutating nature of the call apparent and scopes it to USB connection plus model detection, but it does not say how failure is reported (error versus a status object with a disconnected state) or whether the check is fast/cached.

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?

Two short sentences with no filler; the core action and scope come first, and the supported-model examples follow as useful qualification. Every sentence earns its place.

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 zero-parameter read-only status check with an output schema available to explain return values, the description covers what is needed to decide to call it. The main residual gap is behavior when no calculator is connected, which a richer definition would state.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The description correctly implies the tool needs no input, since it inspects whatever calculator is attached.

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 states a specific verb and resource: checking the USB connection status of a Texas Instruments calculator on the computer, and it adds that it detects models such as TI-Nspire CX II and TI-84 Plus CE. This is clearly distinct from siblings like list_remote_filesystem or capture_screen_live, though no sibling is named explicitly.

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: an agent can infer this is a pre-flight connectivity check before operations like direct_upload_tns or capture_screen_live. There is no explicit when-to-use statement, no mention of prerequisites (USB cable, driver, calculator powered on), and no guidance on what to do if the status reports no 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