Skip to main content
Glama

读取需求发布指南

get_request_guide
Read-onlyIdempotent

按场景读取资料准备、交付和验收方法,包括把“今晚吃什么”等 AI 推荐整理成具体生活需求的示例与草稿入口。仅返回指南,不代替用户发布需求。

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

Input Schema

NameRequiredDescriptionDefault
scenarioNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description usefully confirms it returns only guide content with no publishing side effect, but the mention of a '草稿入口' (draft entry) is ambiguous about whether it hands back a link or performs any action, which slightly muddies the read-only picture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main action is front-loaded, which is good, but the embedded '今晚吃什么' anecdote consumes a large share of a two-sentence description and reads as promotional rather than operational. The closing constraint sentence earns its place; the example sentence only partly does.

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?

For a simple, read-only guide lookup with no output schema, the description conveys enough about what comes back (preparation, delivery, acceptance methods) and that nothing is published. It stops short of describing the scenario categories or what the returned guide actually looks like, which is the main remaining gap.

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 0%, so the description must carry the parameter meaning. It explains that the guide is read by scenario, which clarifies the role of the single `scenario` parameter, but it never explains the six enum values or the 'all' default, leaving the agent to guess what each scenario contains.

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 gives a specific verb and resource (读取…指南) and scopes it by scenario, listing what the guide covers: 资料准备、交付和验收方法. It also draws a boundary against publishing tools, so an agent can tell it apart from search_requests; the '今晚吃什么' example adds noise but does not obscure the core purpose.

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?

The phrase '按场景' implies the guide should be fetched per scenario, and '仅返回指南,不代替用户发布需求' tells the agent this is not the tool for actually publishing a request. However, no alternative is named and no explicit condition is given for choosing among the six scenarios or for when to skip the guide entirely.

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