Skip to main content
Glama

Math.Tools MCP Server

Equation Image Tool

equation-image

Render a math equation (compact LaTeX-like markup) as a PNG image. Requires a math.tools API token (equations:image ability).

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": {
      "equation": "<equation>"
    },
    "name": "equation-image"
  }
}

Input Schema

NameRequiredDescriptionDefault
equationYesThe equation, using math.tools' compact LaTeX-like markup — e.g. 'x^2 - y^2 = (x-y)', 'sqrt{x^2+y^2}'.
fontsizeNoFont size in points. Defaults to the site default; clamped to the supported min/max server-side.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 usefully discloses the auth requirement (API token, equations:image ability) and the output type (PNG), but omits failure behavior for invalid markup, any size/length limits, and rate-limit concerns.

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 sentences, front-loaded with the action and output format, followed by the prerequisite. There is no filler or redundant phrasing.

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?

For a simple two-parameter rendering tool this covers purpose, output type, and auth. However, with no output schema and no annotations, the description should say how the PNG is returned (raw bytes, base64, URL) and what errors look like — that gap leaves an agent guessing at invocation handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are fully documented there, including the server-side clamping of fontsize. The description only restates the "compact LaTeX-like markup" idea already present in the schema, adding no new parameter meaning; baseline 3 applies.

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?

Uses a specific verb ("Render") with a precise resource ("a math equation") and names the output format (PNG), plus the markup dialect used. Nothing in the sibling list (convert-base, gcf-lcm, pi-digits, etc.) overlaps with image rendering, so the scope 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?

The description implies when to use it (you need a rendered equation image) and states a prerequisite — a math.tools API token with the equations:image ability — but gives no explicit when-not guidance or comparison to alternatives. With siblings in a clearly different domain, this is adequate but not instructive.

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