Skip to main content
Glama

Wolfram Compute

wolfram_compute
Read-onlyIdempotent

Evaluate Wolfram Language code in a real Wolfram kernel, symbolic math (Integrate, Solve, DSolve, Simplify, Series, Limit), exact arithmetic, matrix algebra, number theory, unit conversion, and any Wolfram Language expression. Answers "integrate x^2 sin x", "solve this equation symbolically", "eigenvalues of this matrix". Give actual Wolfram Language code. Example: wolfram_compute({ code: "Integrate[x^2 Sin[x], x]" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "Integrate[x^2 Sin[x], x]"
    },
    "name": "wolfram_compute"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesWolfram Language code to evaluate, e.g. "Solve[x^2 + 3x - 4 == 0, x]" or "Eigenvalues[{{1,2},{3,4}}]"
time_constraint_secondsNoEvaluation time limit in seconds, 1-60 (default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "code": "Integrate[x^2 Sin[x], x]"
      +  },
      +  {
      +    "code": "Solve[x^2 + 3*x - 4 == 0, x]"
      +  }
      +]
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds that evaluation happens in a real Wolfram kernel, which signals genuine remote computation rather than a cached lookup. It does not disclose what happens on timeout, error returns, or output format, leaving meaningful behavioral gaps.

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?

The core capability is front-loaded in the first clause, and the domain list plus example questions efficiently convey scope. It is somewhat list-heavy and the inline example call largely duplicates the schema's `examples` block, which is mild waste but not harmful.

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 two-parameter, no-output-schema tool, the description covers what to send but not what comes back — no mention of whether the result is a string, a Wolfram expression, or an error object on timeout or invalid syntax. An agent can construct the call but cannot anticipate the response shape.

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%, so both `code` and `time_constraint_seconds` are already documented with examples and a default. The description's 'Give actual Wolfram Language code' reinforces the format expectation but adds no syntax, escaping, or timeout-behavior detail beyond the schema, so the 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?

States a specific verb and resource ('Evaluate Wolfram Language code in a real Wolfram kernel') and enumerates the concrete capability domains (symbolic math, exact arithmetic, matrix algebra, number theory, unit conversion). The example user questions ('integrate x^2 sin x', 'eigenvalues of this matrix') make the scope unmistakable and clearly separate it from the prediction-market and research siblings.

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 positive guidance: the caller must supply actual Wolfram Language code, illustrated by a concrete call example. It does not state when not to use it or name any alternative for simpler math, so the exclusions side is absent, but the intended usage context is explicit.

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.