Skip to main content
Glama

Search requests

search_requests
Read-onlyIdempotent

Search public software requests. USE WHEN (a) a user is unsatisfied with existing software and you need to check for a similar request before creating one, or (b) a creator wants to discover demand to find or build software for. Optional keyword query, status and platform filters. NO side effects; public. Similar requests are suggestions: compare must_have constraints before treating two requests as the same need. A resolved request carries resolved_by, the software its requester accepted.

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_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo'updated' = most recently changed first; with status 'resolved' that is the most recently resolved.relevance
limitNoPage size (max 50).
queryNoKeywords describing the need.
offsetNoItems to skip; use next_offset from the previous page.
statusNo'active' = open + proposals_available.active
platformNoOnly requests targeting this platform, e.g. 'ios'.
requested_byNoOnly requests published by this user: the `owner.id` of a request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so 'NO side effects; public' is a confirming restatement. The description earns credit for disclosing genuine behavioral context the annotations cannot: that matches are suggestions requiring constraint comparison, and that resolved requests expose a resolved_by field. It does not discuss pagination or ordering semantics beyond the schema.

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?

Front-loads the capability, then the when-to-use conditions, then the interpretation caveat about suggestions and resolved_by. Every sentence carries information and nothing is repeated.

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 search tool with no output schema, the description covers purpose, triggers, result interpretation, and one key return field (resolved_by). Missing only return-shape and pagination detail, which the offset/limit schema partially implies, so completeness is strong but not exhaustive.

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?

With 100% schema description coverage, the schema already documents every filter, enum, and default. The description only summarizes 'optional keyword query, status and platform filters,' adding no syntax, edge cases, or interaction rules beyond the schema. Baseline 3 is appropriate.

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 public software requests') and immediately scopes it as public search over requests, which distinguishes it from get_request (single fetch) and search_software (software records). The two USE WHEN scenarios make the intent unmistakable.

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?

Gives two concrete triggers: checking for a duplicate before creating a request, and a creator exploring demand. It also warns that results are suggestions and must be compared on must_have constraints. It stops short of explicit when-not-to-use guidance relative to siblings such as get_request.

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