Skip to main content
Glama

sindy_run

Read-onlyIdempotent

Sparse Identification of Nonlinear Dynamics (SINDy).

Recovers governing differential equations (dx/dt = f(x)) from time
series data. Returns human-readable sparse expressions. Fast (seconds).
For algebraic y = f(x) relationships without time structure, use
pysr_run instead.

Pricing: free tier up to 100 rows and 8 variables. Beyond that,
$0.05 + $0.01 per 100 extra rows + $0.01 per extra variable squared,
via x402 (USDC on Base) or MPP/Stripe. MPP/Stripe adds a flat $0.35
per-transaction fee (Stripe processing), so the MPP challenge amount
in a `payment_required` response is $0.35 higher than the x402 amount
for the same base price; x402 gets the lower rate. Omit `payment`
for free-tier requests; paid requests without a valid credential
receive a `payment_required` result with pricing and accepted schemes.
Full pricing table as structured JSON: occam://pricing

Advisory limits: jobs over 500,000 rows or 50 variables are accepted
but may not converge within the time budget; the response carries a
top-level `warning` the agent should surface and treat as tentative.

If `feature_names` is supplied, its length must equal the number of
data columns; a mismatch is rejected with a validation error.

Rate limit: 10 requests/hour per IP, 200/hour global, max queue
depth 20 (shared with pysr_run and pysr_uncertainty).

Response (success) includes `equations[]` (each with `variable`,
`equation`, `expression`, `expression_latex`, `r2`), `library_terms`,
`nonzero_terms`, `elapsed_seconds`, `canonical_match` (dict with
`system`, `form`, `variable_map`, `parameter_map`, `confidence` if
the discovered system matches one of Lorenz / Lotka-Volterra /
Van der Pol / Duffing; `null` otherwise), optional `warning`,
optional `_meta` (MPP receipt on paid calls). Full response and
payment-required schemas: occam://tool-schemas

Example request:
  data=[[1.0, 0.0], [0.95, -0.31], [0.81, -0.59]], t=[0.0, 0.1, 0.2],
  feature_names=["x", "y"], poly_degree=2, threshold=0.1

Policy: occam://privacy-policy — Citation: occam://citation-info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tYesTimestamps corresponding to each row of data. Length must match row count.
dataYes2D array of time series data. Each row is a timestep, each column is a state variable. Minimum 3 rows (finite-difference derivative). Free tier: 100 rows, 8 variables. Paid tier: up to 500,000 rows, 50 variables.
paymentNoPayment credential. Accepts either a JSON object or a JSON-encoded string (FastMCP's transport pre-parses strings whose field annotation is non-bare-`str` into objects, so the object form is canonical; the string form is accepted for legacy callers). Required when the dataset exceeds the free tier (100 rows, 8 variables). Omit for free-tier requests. For x402: {"transaction":"0x...","network":"...","priceToken":"..."}. For MPP/Stripe: {"challenge":{...},"payload":"..."}. For prepaid API key: {"scheme":"prepaid","api_key":"occ_live_...","request_id":"<optional uuid>"}.
max_iterNoMaximum STLSQ optimizer iterations. Default 20.
thresholdNoSTLSQ sparsity threshold. Higher values produce sparser equations. Default 0.1.
poly_degreeNoPolynomial library degree for SINDy candidate functions. Default 2.
feature_namesNoNames for each variable/feature column. Defaults to x0, x1, ...

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
warningNo
equationsNo
library_termsNo
nonzero_termsNo
canonical_matchNo
elapsed_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / data / description
      Previous value: -"2D array of time series data. Each row is a timestep, each column is a state variable. Free tier: 100 rows, 8 variables. Paid tier: up to 500,000 rows, 50 variables."New value: +"2D array of time series data. Each row is a timestep, each column is a state variable. Minimum 3 rows (finite-difference derivative). Free tier: 100 rows, 8 variables. Paid tier: up to 500,000 rows, 50 variables."
    • addedInput schema / properties / data / examples
      Added value: +[
      +  [
      +    [
      +      1,
      +      0
      +    ],
      +    [
      +      0.9553,
      +      -0.2955
      +    ],
      +    [
      +      0.8253,
      +      -0.5646
      +    ],
      +    [
      +      0.6216,
      +      -0.7833
      +    ],
      +    [
      +      0.3624,
      +      -0.932
      +    ],
      +    [
      +      0.0707,
      +      -0.9975
      +    ],
      +    [
      +      -0.2272,
      +      -0.9738
      +    ],
      +    [
      +      -0.5048,
      +      -0.8632
      +    ],
      +    [
      +      -0.7374,
      +      -0.6755
      +    ],
      +    [
      +      -0.9041,
      +      -0.4274
      +    ],
      +    [
      +      -0.99,
      +      -0.1411
      +    ],
      +    [
      +      -0.9875,
      +      0.1577
      +    ]
      +  ]
      +]
    • addedInput schema / properties / data / minItems
      Added value: +3
    • addedInput schema / properties / t / examples
      Added value: +[
      +  [
      +    0,
      +    0.3,
      +    0.6,
      +    0.9,
      +    1.2,
      +    1.5,
      +    1.8,
      +    2.1,
      +    2.4,
      +    2.7,
      +    3,
      +    3.3
      +  ]
      +]
    • addedInput schema / properties / t / minItems
      Added value: +3
  2. Changed2 schema fields changed
    • changedInput schema / properties / payment / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / payment / description
      Previous value: -"Payment credential as a JSON string. Required when the dataset exceeds the free tier (100 rows, 8 variables). Omit for free-tier requests. For x402: {\"transaction\":\"0x...\",\"network\":\"...\",\"priceToken\":\"...\"}. For MPP/Stripe: {\"challenge\":{...},\"payload\":\"...\"}."New value: +"Payment credential. Accepts either a JSON object or a JSON-encoded string (FastMCP's transport pre-parses strings whose field annotation is non-bare-`str` into objects, so the object form is canonical; the string form is accepted for legacy callers). Required when the dataset exceeds the free tier (100 rows, 8 variables). Omit for free-tier requests. For x402: {\"transaction\":\"0x...\",\"network\":\"...\",\"priceToken\":\"...\"}. For MPP/Stripe: {\"challenge\":{...},\"payload\":\"...\"}. For prepaid API key: {\"scheme\":\"prepaid\",\"api_key\":\"occ_live_...\",\"request_id\":\"<optional uuid>\"}."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "CanonicalMatch": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "confidence": {
      +          "title": "Confidence",
      +          "type": "number"
      +        },
      +        "form": {
      +          "title": "Form",
      +          "type": "string"
      +        },
      +        "parameter_map": {
      +          "additionalProperties": {
      +            "type": "number"
      +          },
      +          "title": "Parameter Map",
      +          "type": "object"
      +        },
      +        "system": {
      +          "title": "System",
      +          "type": "string"
      +        },
      +        "variable_map": {
      +          "additionalProperties": {
      +            "type": "string"
      +          },
      +          "title": "Variable Map",
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "system",
      +        "form",
      +        "variable_map",
      +        "parameter_map",
      +        "confidence"
      +      ],
      +      "title": "CanonicalMatch",
      +      "type": "object"
      +    },
      +    "SindyEquation": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "equation": {
      +          "title": "Equation",
      +          "type": "string"
      +        },
      +        "expression": {
      +          "title": "Expression",
      +          "type": "string"
      +        },
      +        "expression_latex": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "title": "Expression Latex"
      +        },
      +        "r2": {
      +          "title": "R2",
      +          "type": "number"
      +        },
      +        "variable": {
      +          "title": "Variable",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "variable",
      +        "equation",
      +        "expression",
      +        "expression_latex",
      +        "r2"
      +      ],
      +      "title": "SindyEquation",
      +      "type": "object"
      +    }
      +  },
      +  "additionalProperties": true,
      +  "properties": {
      +    "canonical_match": {
      +      "anyOf": [
      +        {
      +          "$ref": "#/$defs/CanonicalMatch"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null
      +    },
      +    "elapsed_seconds": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Elapsed Seconds"
      +    },
      +    "equations": {
      +      "anyOf": [
      +        {
      +          "items": {
      +            "$ref": "#/$defs/SindyEquation"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Equations"
      +    },
      +    "library_terms": {
      +      "anyOf": [
      +        {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Library Terms"
      +    },
      +    "nonzero_terms": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Nonzero Terms"
      +    },
      +    "warning": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Warning"
      +    }
      +  },
      +  "title": "SindyRunResult",
      +  "type": "object"
      +}
  4. Changed2 schema fields changed
    • changedInput schema / properties / data / description
      Previous value: -"2D array of time series data. Each row is a timestep, each column is a state variable. Max 10,000 rows, 20 variables."New value: +"2D array of time series data. Each row is a timestep, each column is a state variable. Free tier: 100 rows, 8 variables. Paid tier: up to 500,000 rows, 50 variables."
    • addedInput schema / properties / payment
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Payment credential as a JSON string. Required when the dataset exceeds the free tier (100 rows, 8 variables). Omit for free-tier requests. For x402: {\"transaction\":\"0x...\",\"network\":\"...\",\"priceToken\":\"...\"}. For MPP/Stripe: {\"challenge\":{...},\"payload\":\"...\"}.",
      +  "title": "Payment"
      +}
  5. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds substantial behavioral context: pricing tiers and payment schemes, rate limits, advisory convergence warnings, validation errors (feature_names mismatch), and the structure of success and payment_required responses. Nothing contradicts annotations; the description enriches them.

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 long but well-structured: it leads with the core purpose, then pricing, advisories, validation, rate limits, response schema, and an example. While verbose, each section carries necessary operational detail for a commercial tool. It is front-loaded and organized, though could be tightened without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description goes beyond it to explain response contents (equations, canonical_match, warnings, _meta), payment-required behavior, validation errors, rate limits, and pricing. Combined with the schema, an agent has virtually everything needed to call the tool correctly, including edge cases and failure modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameters are already documented. The description adds value beyond the schema by explaining free-tier limits on the 'data' parameter, the exact validation rule for 'feature_names', and the full semantics of the 'payment' parameter (x402 vs MPP/Stripe formats and pricing implications). This goes beyond the schema's basic type/description info.

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?

The description clearly states the tool recovers governing differential equations from time series data via SINDy, and explicitly contrasts with pysr_run for algebraic relationships. It names the specific method and output, making it immediately distinguishable from siblings.

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?

It provides explicit when-to-use guidance (time series data for differential equations), explicitly directs users to pysr_run for non-time-structured algebraic problems, and includes detailed free/paid tier rules, rate limits, and advisory limits. Alternatives and exclusions are unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources