Skip to main content
Glama

ode_solve

Read-onlyIdempotent

Solve ordinary differential equations numerically with Euler or RK4 methods by providing dy/dt as a JS expression in terms of t and y.

Instructions

Solve an ordinary differential equation numerically using Euler or RK4 method. Provide the ODE as a JS expression in terms of t and y.

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": {
      "expression": "<expression>"
    },
    "name": "ode_solve"
  }
}

Input Schema

NameRequiredDescriptionDefault
t0NoInitial time (default 0)
y0NoInitial value y(t0) (default 1)
stepsNoNumber of steps (default 100, max 10000)
t_endNoEnd time (default 1)
methodNoIntegration method (default rk4)
expressionYesJS expression for dy/dt in terms of t and y, e.g. 't + y'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld. The description adds the choice of Euler/RK4 methods, but it does not explain security implications of evaluating a JS expression, accuracy/performance tradeoffs, or handling of invalid expressions—context that would be especially valuable given openWorldHint.

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 core action and the key input requirement. No filler or redundancy.

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?

For a numerical solver with no output schema, the description leaves a significant gap: it does not say what the tool returns (e.g., array of solution points vs. final value) or how results are shaped. The parameter defaults are covered by the schema, but the missing return-value semantics limits an agent's ability to use the output 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 description coverage is 100%, so all six parameters are documented there. The description only repeats that the expression is a JS expression in t and y; it adds no new meaning about t0, y0, steps, t_end, or method defaults beyond what the schema provides.

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 verb and resource ('Solve an ordinary differential equation numerically') and names the two supported methods. It is clearly distinguishable from nearby math tools like numerical_integrate (which integrates a given function) and numerical_diff.

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 when to use it via the ODE context and gives a required input format ('JS expression in terms of t and y'), but it does not say when to prefer this over related numerical tools or mention any exclusions. Usage is inferable but not explicitly guided.

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