Skip to main content
Glama

Monte statistics

List solvers

list_solvers
Read-onlyIdempotent

The 11 solvers and the inputs each one takes (key, label, default value, and choices where there are some). Use with solve.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_solvers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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), so the bar is lower. Beyond that, the description discloses the shape of the returned data — per-solver input entries with key, label, default value, and choices where applicable — which is genuinely useful since no output schema exists. It does not say whether the solver set is static or configurable per account, a minor gap.

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 short sentences, front-loaded with what the tool returns, followed by the one relational hint that matters ('use with solve'). The parenthetical enumerates the returned fields compactly rather than padding with prose. Nothing could be cut without losing information.

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?

For a no-parameter, read-only discovery tool with rich annotations, the description supplies the essential missing piece: what the response contains. An agent can decide to call it and interpret the result without further context. A note on usage example or whether results are cached/static would close the remaining gap.

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?

The schema has zero properties and 100% coverage, so there is nothing for the description to disambiguate at the parameter level. Baseline for a no-parameter tool applies, and nothing in the description misleads about inputs.

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?

The description names the resource (the 11 solvers) and states exactly what it exposes: the inputs each solver takes, with key, label, default value, and choice lists. That is specific enough to distinguish it from siblings like list_topics or get_topic, which are not about solver inputs. It does not literally say 'list' or 'returns', but the enumeration framing makes the read intent unambiguous.

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?

'Use with solve' is a real usage signal: it tells the agent this is the discovery companion for the solve tool. However, it stops short of stating the condition explicitly (e.g., call this before solve to learn valid solver keys and input shapes) and offers no exclusions or comparison to other list tools. The guidance is implied rather than spelled out.

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