Skip to main content
Glama
XBP-Europe

SageMath MCP Server

by XBP-Europe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

plot3d_expression

Idempotent

Render a 3D surface plot from a two-variable expression, with custom variable names, ranges, and PNG or SVG output.

Instructions

Plot a 3D surface of a two-variable expression as a rendered image

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
expressionYesExpression of two variables (e.g. 'sin(x)*cos(y)')
x_variableNoFirst variablex
y_variableNoSecond variabley
x_range_maxNoX upper bound
x_range_minNoX lower bound
y_range_maxNoY upper bound
y_range_minNoY lower bound
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

B3.3/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds only the return modality ('rendered image'), which is useful but thin; it says nothing about what the image represents, whether a session must exist, or how results are delivered beyond the schema-documented image_format.

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?

A single sentence with the verb front-loaded and zero filler. Everything an agent needs at a glance is present.

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?

With no output schema, the description should clarify what the 'rendered image' return actually is (inline blob, file path, or URL), and it does not. Annotations and the exhaustive schema cover safety and inputs, so it is adequate but leaves the output contract underspecified for a 9-parameter tool.

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 description coverage is 100%, so every parameter is already documented in the schema, including the session/workspace semantics and image_format enum. The description only reinforces that expression takes two variables, which the schema already conveys. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource: 'Plot a 3D surface of a two-variable expression.' The qualifiers '3D' and 'two-variable' implicitly separate it from the sibling plot_expression and plot_multi_expression, but no sibling is named, so the distinction must still be inferred.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance. The '3D' and 'two-variable' phrasing hints at when this tool is appropriate over 2D plotting siblings, but no alternatives are named and no exclusion or scenario conditions are stated.

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