Skip to main content
Glama

search_problems

Read-onlyIdempotent

Finds coding problems on a platform by required tags and difficulty level, with an option to exclude problems already solved by a specified handle.

Instructions

Problems having every tag given, at the level given. Take tags and levels from list_platforms or from problems the platform returned. With exclude_solved_by, skips that handle's solved problems.

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": {
      "platform": "<platform>"
    },
    "name": "search_problems"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
levelNo
limitNo
platformYes
exclude_solved_byNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedOutput schema / $defs / Problem / properties / source
      Added value: +{
      +  "default": "platform",
      +  "title": "Source",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine behavior beyond that: tags are conjunctive ("every tag given") and exclude_solved_by drops a specific handle's solved problems. It still says nothing about ordering, pagination behavior implied by limit, or result truncation.

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?

Three short sentences, front-loaded with the filtering semantics and then the parameter-sourcing hint; nothing is padded. The first sentence is a grammatical fragment (no verb), which slightly costs readability but not length.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. Still, for a 5-parameter tool with 0% schema coverage, an agent is left guessing what `platform` expects and what `limit` does, which the description should have closed.

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

Parameters3/5

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

Schema description coverage is 0%, so the description carries the burden and does partially compensate: it clarifies the AND semantics of `tags`, ties `level` to values from list_platforms, and explains `exclude_solved_by`. It leaves the required `platform` parameter and `limit` entirely unexplained, so roughly half the parameter space remains undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment "Problems having every tag given, at the level given" conveys the resource (problems) and the AND-of-tags filtering semantics, but never states a clear verb or that results are a search/list. An agent can infer the purpose from the name plus this text, but the sentence does not stand on its own as a purpose statement.

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?

"Take tags and levels from list_platforms or from problems the platform returned" usefully tells the agent where valid filter values come from, which is real guidance. However, there is no explicit when-to-use versus siblings (e.g., list_mistakes or mistake_patterns) and no when-not guidance, so usage is only implied.

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