Skip to main content
Glama
morluto

jacobian

by morluto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
math.findA

Find or inspect public Jacobian MCP operations.

Forms:

  • query: describe one local mathematical need in ordinary language. namespace, limit, and cursor are optional search controls. Preserve established mathematical names from the task, the supplied objects and constraints, the requested computation or decision, the full scalar, batch, or exhaustive scope, and whether the requested result is a value, witness, certificate, obstruction, profile, or complete enumeration. Do not replace a supplied named property only with its expanded definition, translate the need into catalog tags, or submit the surrounding proof goal.

  • operation_id: pass one exact operation ID to receive its authoritative input and output schemas, operator-authored examples, and current optional backend availability. Matches expose static runtime_requirements; inspection checks these runtimes in the server environment.

For matching, use namespace only when the primary operation-ID namespace is already known with high confidence. Matching returns 10 candidates by default; request up to 20 when a wider first page is useful. Follow next_cursor with the same need and namespace to continue. Ordered matches are deterministic retrieval candidates, not applicability claims; inspect a promising operation before math.run. Read operation://catalog only when the complete bulk catalog is genuinely needed.

Examples:

  • {"query":"exact determinant of a rational matrix","namespace":"matrix","limit":3}

  • {"operation_id":"polynomial.compute.gcd"}

math.runA

Run one installed math tool by ID with its typed payload. A successful call returns the operation-owned canonical mathematical value in output; a later inspected operation may accept that complete value unchanged. Read its fields to determine what the calculation established. MCP reports malformed payloads, unknown IDs, and host failures as tool errors, not as mathematical results. If the payload shape is unknown, inspect the exact operation with math.find. When it publishes an examples item, copy and adapt that item's input object as the payload; otherwise, form the payload from the input schema and its field descriptions. Do not call math.run with an empty payload merely to discover required fields; inspection is authoritative.

Timeout, incomplete search, and missing witnesses appear only in the concrete domain result that owns them; none is a mathematical conclusion by itself.

Examples:

  • {"operation_id":"integer.compute.extended_gcd","payload":{"left":"84","right":"30"}}

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
operation-catalogLarge exact bulk export of every installed operation, schema, and example. Use math.find for ordinary operation discovery and inspection. If matching fails, refine or paginate math.find; read this resource only when the task requires the complete inventory.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools occupy clearly separate phases: math.find is for discovery and inspection, while math.run is for execution. Their inputs and outputs are distinct, so an agent selecting between them has no real ambiguity.

Naming Consistency5/5

Both tool names share the same math. namespace and follow a simple verb pattern: find and run. This creates a predictable, uniform naming convention with no mixed styles.

Tool Count4/5

Two tools is slightly below the typical MCP tool count, but it is proportionate to this server's dispatcher design: discovering/inspecting operations and executing them are the two essential capabilities. Each tool is necessary and neither is redundant.

Completeness5/5

The apparent domain is a registry/executor for public math operations, and math.find plus math.run covers the full discover-inspect-execute lifecycle. The catalog can be accessed through find, and run handles execution, so there are no obvious dead ends or missing operations.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources