Skip to main content
Glama
XBP-Europe

SageMath MCP Server

by XBP-Europe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

coding_theory_operation

Idempotent

Compute error-correcting code parameters—length, dimension, minimum distance, rate, and generator matrix—for Hamming and generalized Reed-Solomon codes.

Instructions

Error-correcting codes: length, dimension, minimum distance, rate and generator matrix for Hamming and generalized Reed-Solomon codes. Prefer this over evaluate_sage for code parameters.

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
code_typeYesCode constructor, e.g. 'HammingCode(GF(2),3)', 'GeneralizedReedSolomonCode(GF(7).list()[:6],3)'
operationYesOne of: length, dimension, minimum_distance, generator_matrix, rate

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.0
    • 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'."
  2. Changed2 schema fields changedv0.5.0
    • changedInput schema / properties / code_type / description
      Previous value: -"Code constructor, e.g. 'HammingCode(GF(2),3)', 'ReedSolomonCode(GF(7),3,5)'"New value: +"Code constructor, e.g. 'HammingCode(GF(2),3)', 'GeneralizedReedSolomonCode(GF(7).list()[:6],3)'"
    • 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

A4.2/5.0
Behavior3/5

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

Annotations declare idempotent=true, destructive=false, openWorldHint=false, and readOnlyHint=false. The description adds domain scope but no behavioral details beyond annotations, such as workspace state effects or session handling. With annotations covering the safety profile, this is adequate but not rich.

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 tool's purpose and immediately followed by sibling routing. No filler or redundant text.

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?

Output schema exists, so return values need not be explained. Annotations cover safety and idempotency. The description is complete for calling the tool, though it could clarify whether code_type accepts arbitrary Sage constructors or only the named families.

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 parameters are fully documented by the schema. The description enumerates operations that match the schema enum and lists code families that match the schema examples, adding little beyond what is already structured.

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 domain (error-correcting codes) and enumerates the exact computed quantities: length, dimension, minimum distance, rate, generator matrix. It also names supported code families (Hamming, generalized Reed-Solomon) and explicitly distinguishes itself from evaluate_sage.

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

Usage Guidelines5/5

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

Includes an explicit routing directive: 'Prefer this over evaluate_sage for code parameters.' This tells the agent exactly when to choose this tool over a sibling without requiring inference.

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