Skip to main content
Glama

open_problems

Read-only

Statements not recorded as solved, most valuable prize first. Use formalised_only to restrict to those a prover could attempt directly.

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": "open_problems"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
min_prizeNo
collectionNo
formalised_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true, so safety is already covered. The description adds genuinely useful behavior: the result is sorted by prize value descending and the filter is semantic ('not recorded as solved') rather than a raw flag. It says nothing about pagination behavior for limit or whether the ordering is stable/global across collections.

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, zero filler, and the result-set definition is front-loaded before the optional filter advice. Every clause adds information the schema does not carry.

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?

This is a simple read-only listing tool with no output schema, and the description covers the core semantics and ordering. However, with an undocumented four-parameter schema and no explanation of what a 'statement' or 'prize' record contains, an agent must infer a fair amount before invoking it confidently.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description carries the full burden and only clarifies one (formalised_only). limit, min_prize, and collection are left entirely to their names, and the relationship between 'most valuable prize first' and min_prize is never made explicit.

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 a specific resource and scope ('statements not recorded as solved') and adds an ordering rule ('most valuable prize first'), so the agent knows exactly what set is returned. It does not explicitly contrast itself with siblings such as search_statements or get_statement, leaving that differentiation implicit.

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 second sentence gives conditional guidance, but only for one parameter: use formalised_only when the caller wants statements a prover could attempt directly. There is no statement of when to prefer this tool over search_statements or get_target, and no exclusions or prerequisites are mentioned.

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