Skip to main content
Glama
XBP-Europe

SageMath MCP Server

by XBP-Europe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Plot Expression

plot_expression
Idempotent

Plot any mathematical expression and get a rendered PNG or SVG image. Specify the variable and plot range to visualize functions clearly.

Instructions

Plot an expression and return it as a rendered image (PNG or SVG)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionNoWorkspace to use, as a name or a portable handle. Workspaces have independent variables. A name is scoped to this MCP session; a handle returned by start_sage_session (workspace_token) reaches the same workspace across reconnects and is a bearer credential -- keep it secret. Omit for 'default'.default
variableNoPlot variablex
range_maxNoUpper bound of plot range
range_minNoLower bound of plot range
expressionYesExpression to plot
image_formatNoImage format to return: 'png' (raster) or 'svg' (vector, smaller)png

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.0
    • addedInput schema / properties / image_format
      Added value: +{
+  "default": "png",
+  "description": "Image format to return: 'png' (raster) or 'svg' (vector, smaller)",
+  "enum": [
+    "png",
+    "svg"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / session / description
      Previous value: -"Named workspace to use. Workspaces have independent variables; omit for 'default'."New value: +"Workspace to use, as a name or a portable handle. Workspaces have independent variables. A name is scoped to this MCP session; a handle returned by start_sage_session (workspace_token) reaches the same workspace across reconnects and is a bearer credential -- keep it secret. Omit for 'default'."
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / session
      Added value: +{
+  "default": "default",
+  "description": "Named workspace to use. Workspaces have independent variables; omit for 'default'.",
+  "type": "string"
+}
  3. First observedv0.3.1

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the tool is a safe, non-destructive operation. The description adds that it returns a rendered image in PNG or SVG formats, which is beyond the schema. It does not mention side effects or resource limitations, but for a plotting tool this is sufficient.

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 description is a single sentence, efficient and to the point. It is appropriately front-loaded with the primary action and output. No wasted words, though it could arguably include a brief note about usage context without bloating.

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?

Given a relatively simple tool with a clear schema and no output schema, the description covers the core function and output. It lacks explicit guidance on how the expression should be formatted (e.g., valid Sage syntax), but the schema and sibling names provide context. For a standard plotting tool, this is adequate.

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 all six parameters are described in the schema. The description adds general context (plotting an expression) but does not add details about parameter interactions or syntax beyond what the schema already provides. Baseline 3 is appropriate because the schema carries the detail.

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?

The description clearly states the action (plot) and the resource (expression), and mentions the output format (rendered image). It is specific enough to distinguish from most siblings, though sibling tools like plot3d_expression and plot_multi_expression are not explicitly differentiated.

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 usage for plotting an expression, but does not explicitly state when to use this tool versus alternatives like plot3d_expression or plot_multi_expression. No exclusions or conditions are mentioned, leaving the agent to infer based on tool names.

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