Skip to main content
Glama

Intex Institute

Read a formula

read_formula
Read-onlyIdempotent

One LaTeX formula in (math mode, no dollar signs). Back come what it reads as, the words a screen reader says for it, the text it copies out as, and its MathML. Free without a key, thirty formulas every ten minutes; with a key, a tenth of a cent each.

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": {
      "tex": "<tex>"
    },
    "name": "read_formula"
  }
}

Input Schema

NameRequiredDescriptionDefault
texYesThe formula, for example \frac{a}{b} or e^{i\pi} + 1 = 0.

Output Schema

NameRequiredDescriptionDefault
copyNo
mathmlNo
speechNo
formulaNo
reads_asNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), so the bar is lower, and the description still adds real operational context: a 30-per-10-minute free quota and a per-call price with a key. What it does not mention is failure behavior on malformed LaTeX, which would have pushed this higher.

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?

Three short sentences, front-loaded with the input contract before outputs and then pricing. The phrasing 'Back come what it reads as' is slightly informal but compact; nothing is redundant given that the output schema exists, though the output enumeration arguably restates it.

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 single-parameter, read-only transformation tool with an output schema and full annotation coverage, the description covers input format, quota, and cost. Only error handling for invalid LaTeX is left unaddressed, which is a minor gap at this complexity level.

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 coverage is 100% and the schema already carries an example, so baseline would be 3. The description earns the extra point by supplying constraints the schema lacks: exactly one formula, math mode only, and no surrounding dollar signs — the most common call-time error for this input type.

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 the resource precisely (one LaTeX formula in, four derived renderings out: read-aloud form, screen-reader words, copy text, MathML) so the agent can tell this apart from sibling accessibility/PDF tools. The verb is implied rather than stated outright, but the input-output contract is unambiguous.

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?

It gives useful preconditions — a single formula in math mode with no dollar signs, and the generous free tier — but never says when to reach for this instead of the sibling tools (e.g. for single formulas rather than whole documents). The usage context is implied rather than contrasted against alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources