Skip to main content
Glama
Sign In
mathematica-mcp

mathematica-mcp

by yhbcode000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Look up Wolfram Language symbol information

mathematica_information

Inspect Wolfram Language symbols to retrieve attributes, context, option counts, and definitions, helping you discover how to use built-in functions such as Plot or Table.

Instructions

Return information about Wolfram Language symbols: attributes, context, option count and definitions (for user-defined symbols). Useful for discovering how to use a built-in function such as Plot or Table.

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": {
      "symbols": "<symbols>"
    },
    "name": "mathematica_information"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesSymbol names to inspect, e.g. ["Plot", "Table", "Integrate"]. Context-qualified names such as "Global`f" are allowed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full disclosure burden. It usefully enumerates returned fields and notes definitions apply to user-defined symbols, implying a read-only inspection, but it does not state behavior for missing symbols, whether evaluation is triggered, or any permission/rate-limit context.

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 return content and followed by a concrete use case. Every sentence earns its place with no filler.

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 simple one-parameter lookup, the description covers what is returned and gives a concrete usage example, while the schema handles input semantics. It lacks detail on output shape and edge cases, but is complete enough for an agent to invoke correctly.

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 the single symbols parameter is already fully documented in the schema with examples and context-qualified names. The description adds no additional parameter syntax or constraints beyond what the schema provides, so the baseline 3 is appropriate.

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: return information about Wolfram Language symbols, and enumerates the returned data (attributes, context, option count, definitions). It is substantively distinct from evaluate/export/kernel_status, though it does not name those siblings explicitly.

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 a clear use case: discovering how to use a built-in function such as Plot or Table. It does not state when to prefer alternatives or any exclusions, so it stops short of full when/when-not guidance.

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

Deploy Server

Other Tools