Skip to main content
Glama

Equation.io

by io.equation
OverviewDiscussionsAdmin

Show an interactive graph

show_graph
Read-onlyIdempotent

Display an interactive equation.io graph inside the conversation, with editable equations, sliders, pan/zoom, and 3D rotation. Use when the user asks to see or explore a graph. Pass the COMPLETE graph as "equations", one equation or definition per string, preserving unchanged rows when editing. For a slider use "a = 2" then "y = a sin(x)". For advanced syntax read the "syntax" resource (https://equation.io/llms.txt). Returns per-row validation and share links; a row with status "error" is not drawn until its text is corrected and the graph resubmitted. Use encode_graph_url for validation or link-only requests (including share-link preview notes). In clients without UI support, provide share_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
equationsYesEvery equation in the graph, in display order. One equation or definition per string — do not join rows with ";" (inside quoted text a ";" is data, and kept).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesGraph URL using a #-fragment.
rowsYes
validYes
share_urlYesShareable /g/ graph URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / preview
      Removed value: -{
-  "description": "Static preview availability and limitations.",
-  "type": "string"
-}
    • removedOutput schema / properties / preview_omits
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "row": {
-        "type": "string"
-      },
-      "why": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "row",
-      "why"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • changedOutput schema / required
      Previous value: -[
-  "valid",
-  "url",
-  "share_url",
-  "preview",
-  "rows"
-]New value: +[
+  "valid",
+  "url",
+  "share_url",
+  "rows"
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely non-obvious behavior: per-row validation results, share links, and that a row with status 'error' is not drawn until corrected and resubmitted. The no-UI fallback (share_url) is also disclosed.

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?

Front-loaded with purpose then usage then mechanics; dense but nearly every sentence carries actionable detail (completeness, slider pattern, error-row behavior, fallback). Slightly long, with the semicolon note partially duplicating the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-required-parameter tool with an output schema, the description covers invocation, editing semantics, error handling, sibling routing, and client-capability fallback. Nothing an agent needs to call it correctly is missing.

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%, so baseline is 3, but the description adds real meaning: the graph must be COMPLETE, unchanged rows should be preserved when editing, and it supplies a worked slider example ('a = 2' then 'y = a sin(x)'). That is more than the schema conveys, though the semicolon guidance overlaps with the schema text.

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?

States a concrete verb+resource ('Display an interactive equation.io graph inside the conversation') and enumerates the capability set (editable equations, sliders, pan/zoom, 3D rotation). It also implicitly separates itself from the encode/decode siblings by naming encode_graph_url for validation/link-only work.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit trigger ('Use when the user asks to see or explore a graph') plus an explicit alternative and its condition ('Use encode_graph_url for validation or link-only requests'). It even covers the fallback path for clients without UI support.

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

All Equation.io toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources