Skip to main content
Glama

搜索公开需求

search_requests
Read-onlyIdempotent

在最近最多 200 条未取消需求的公开摘要中搜索,可按关键词、分类、进度和交付方式筛选。

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
limitNo
queryNo标题或分类中的关键词,例如 球搭子、收纳、配件。
offsetNo
statusNo
categoryNo
deliveryModeNo
solutionTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description nevertheless adds genuinely useful behavior beyond them: results are limited to public summaries, cancelled requests are excluded, and the result window is capped at the 200 most recent. It says nothing about ordering or what a returned summary contains, but the added scoping is real value.

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?

One sentence, front-loaded with the scope limit and then the filter surface, with no filler or restatement of the title. Every clause carries information an agent needs to calibrate its query.

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 seven optional parameters, no required fields, no output schema and rich enum coverage in the schema itself, the description supplies the essentials: what corpus is searched, its hard size limit, and the exclusion of cancelled items. The gaps are the unmentioned solutionType filter and the absence of any paging/ordering note, which keep it from being fully self-sufficient.

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 only 14%, so the description must carry weight; it names four filters (keyword, category, status, delivery mode) mapping to query, category, status and deliveryMode. It leaves solutionType, limit and offset unexplained, and does not clarify that keyword matching is limited to title or category. Useful but partial compensation for the coverage gap.

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?

Uses a specific verb+resource ("在...公开摘要中搜索" / search public summaries) and adds a precise scope constraint: the most recent up to 200 non-cancelled requests. The filter dimensions are named, so an agent knows what kind of tool this is without opening the schema. It stops short of naming how it differs from the listed siblings, so not a 5.

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 rather than stated: a search tool with named filters, plus the implicit constraint that anything older than the 200 most recent or cancelled is unreachable. There is no explicit when-to-use/when-not guidance and no pointer to an alternative tool (e.g. a full-text or detail lookup) for the cases this cap excludes.

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