Graph Paper

Explain a computation

explain

Read-only

Needs sign-in: Show the Compute Engine's own step-by-step working for an operation on a LaTeX expression, so you can relay the steps instead of inventing them. operation is one of "simplify", "solve" (latex must be an equation, e.g. "x^2=4"), "D" (differentiate) or "Integrate". With documentId, it sees that document's definitions. Returns { operation, initial, result, steps: [{ latex, description }] }; relay the steps in order, never fabricate them.

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": "<latex>",
      "operation": "<operation>"
    },
    "name": "explain"
  }
}

Input Schema

Name	Required	Description
`latex`	Yes	The expression (or equation, for "solve") to explain, in LaTeX.
`operation`	Yes	Which working to trace: "simplify", "solve" (an equation), "D" (a derivative), or "Integrate".
`documentId`	No	The id of a document (from list_documents or search_documents). With it, the expression sees that document's definitions; without it, an empty scope.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the readOnly/openWorld annotations it adds an auth requirement ('Needs sign-in'), the exact return shape ({ operation, initial, result, steps }), and an explicit behavioral instruction to relay steps in order and never fabricate them. That is meaningful context the annotations do not carry.

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?

Single dense paragraph that front-loads the auth note and the core purpose before listing operations and return shape. Nothing is wasted, though the operation/return clauses could be broken out for faster scanning.

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?

With no output schema, the description supplies the response structure itself, plus auth, operation semantics, equation requirement, and document scoping. An agent has everything needed to call and interpret it correctly.

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 3 is the floor, but the description adds real value: it names the four valid operations and adds the constraint that 'solve' requires an equation with a concrete example ('x^2=4'), which the schema only alludes to.

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?

States a specific verb and resource: show the Compute Engine's step-by-step working for an operation on a LaTeX expression. The clause 'so you can relay the steps instead of inventing them' implicitly distinguishes it from evaluate-style siblings, but no sibling is named explicitly, so differentiation is only partial.

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

Usage Guidelines4/5

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

Gives clear conditions: use it when you need the engine's own working to relay, requires sign-in, and documentId scopes it to a document's definitions. It does not explicitly exclude or contrast with siblings like evaluate_math or evaluate_steps, so there is no stated alternative path.

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

All Graph Paper tools Inspect

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

Need Help?