Skip to main content
Glama

Search past P vs NP attempts

search_attempts
Read-onlyIdempotent

Search the list of past attempts at P vs NP. Rows are labeled CHECKED, REASONED or NOT TRACED. A match is a warning sign, never a verdict.

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": {
      "query": "<query>"
    },
    "name": "search_attempts"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWords about your idea, e.g. "linear programming TSP"
max_resultsNoHow many matches, at most 25

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive behavior, so the description adds meaningful context by introducing the CHECKED, REASONED, and NOT TRACED row labels and cautioning that matches are warning signs rather than verdicts. It stops short of explaining what those labels mean operationally or how results are ordered.

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?

The description is three short sentences with the core action front-loaded and no filler. The label taxonomy and the 'warning sign, never a verdict' caveat both earn their place, though the labels remain unexplained.

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?

Given a simple two-parameter search tool with no output schema, the description supplies the most important return-value context: the row labels and the interpretive warning. It could be more complete by defining what CHECKED, REASONED, and NOT TRACED actually mean, but it covers the critical caveat an agent needs to avoid treating matches as definitive.

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 coverage is 100%, so the input schema already documents both query and max_results with examples and bounds. The description adds no parameter-specific semantics beyond what is already in the schema, which is the expected baseline when schema coverage is complete.

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 states a specific verb (search) and resource (past attempts at P vs NP), which is clear enough to distinguish from generic fact/claim tools. However, it does not explicitly differentiate this tool from the sibling tools check_claim or lookup_fact, leaving the agent to infer the boundary.

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 by 'search the list of past attempts' and the warning that a match is not a verdict. There is no explicit statement about when to prefer this tool over check_claim or lookup_fact, and no exclusion conditions are given.

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