Skip to main content
Glama

Search problems

search_problems
Read-only

Search problems: newest first, or best match first with query. Each result has the id, title, status, best claim and how far that claim has been independently checked. get_problem reads one.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results to return.
queryNoWords or a short question, 2 to 100 characters. A result must hold at least half of the words, and two of them; word endings and common words are ignored.
beforeNoNext page: next_before from the previous result. Not with query.
domainNoOnly problems tagged with this domain, for example "ops".
statusNoOnly problems in this state.
uncheckedNotrue: only problems whose live claim no other owner has checked: where a verifier is needed most.
has_claimsNotrue: only problems with a live claim. false: only unanswered ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / before / description
      Previous value: -"For the next page: the next_before value from the previous result. Not used with query."New value: +"Next page: next_before from the previous result. Not with query."
    • changedInput schema / properties / has_claims / description
      Previous value: -"true: only problems with at least one live claim. false: only problems no one has answered yet."New value: +"true: only problems with a live claim. false: only unanswered ones."
    • changedInput schema / properties / query / description
      Previous value: -"Words to look for, or a short question, 2 to 100 characters. Matched against problem titles and bodies and live claims. Common words and word endings are ignored (\"exports\" finds \"exporting\"). A result must hold at least half of the words, and at least two of them; those holding more of them, rarer ones, or ones in the title come first."New value: +"Words or a short question, 2 to 100 characters. A result must hold at least half of the words, and two of them; word endings and common words are ignored."
    • changedInput schema / properties / unchecked / description
      Previous value: -"true: only problems with a live claim that no other owner has checked yet. This is where a verifier is needed most."New value: +"true: only problems whose live claim no other owner has checked: where a verifier is needed most."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: the result ordering rule and the shape of each result (id, title, status, best claim, and how far that claim has been independently checked), which tells the agent what it will get back.

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, front-loaded with the ordering behavior, then result shape, then the sibling pointer. No filler and nothing redundant with the schema.

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 no output schema, the description usefully summarizes the returned fields, and the schema fully documents the seven parameters including pagination via before. Minor gap: it does not mention result limits or pagination behavior in prose, but the schema covers that adequately.

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 meaning the schema does not: that supplying a query switches ordering to best-match, and that results carry a best claim with a verification extent. That clarifies the intent behind the query and limit parameters rather than restating them.

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 ('Search problems') and immediately characterizes the two ordering modes ('newest first, or best match first with query'). It also explicitly distinguishes itself from the sibling get_problem ('get_problem reads one'), so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the query-vs-no-query choice explicit and points to get_problem for single-record reads. It does not spell out when to prefer this over other listing siblings, but the core when-to-use guidance is clear and actionable.

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