Skip to main content
Glama

Monte statistics

Solve a problem

solve
Read-onlyIdempotent

Runs one of Monte's solvers and returns every answer with its working, exactly as the solver page shows it. Inputs you leave out keep the solver's defaults. Numbers may be written as 0.7, 70% or 7/10.

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": {
      "solver": "<solver>"
    },
    "name": "solve"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsNoInput key to value, as text, for example {"mu": "500", "sd": "20"}
solverYesSolver id from list_solvers, like tree, normal or ci

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: the return is the full answer set with working, mirroring the solver page. It also discloses that omitted inputs fall back to solver defaults and that numbers can be given in three notations, which an agent cannot infer from annotations.

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?

Three short sentences, each earning its place: what it does, the defaulting rule, and accepted number formats. The most important fact (it runs a solver and returns full working) is front-loaded with no preamble.

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?

With only two parameters, full schema coverage, and no output schema, the description supplies the missing return-value picture ('every answer with its working') and the defaulting behavior. It is nearly complete; only error handling and solver-id discovery are unaddressed.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: omitted input keys silently inherit solver defaults, and numeric values accept decimal, percent, or fraction forms. The free-form text key/value nature of inputs is explained further by the schema example.

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?

States a specific verb and resource: runs a named solver and returns every answer with its working. It is unambiguous what the tool does, though it never names a sibling such as list_solvers or test_result to differentiate itself; that routing cue lives only in the schema's solver field.

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?

Usage is implied (call it to solve a problem with a given solver id) but there is no explicit when-to-use or when-not-to-use guidance. The description does not tell the agent to discover solver ids via list_solvers first, nor when to prefer ab_test or test_result instead, leaving that to the schema.

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