baidu_nlp
Segments Chinese text into words and tags each with its part of speech. Enables text analysis and understanding.
Instructions
[NLP] 词法分析(分词+词性标注) — $0.01/call (free: 5/5 today)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | 待分析文本 |
Segments Chinese text into words and tags each with its part of speech. Enables text analysis and understanding.
[NLP] 词法分析(分词+词性标注) — $0.01/call (free: 5/5 today)
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | 待分析文本 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided. The description does not disclose behavioral traits such as whether it is read-only, rate limits, authentication needs, or side effects. The only extra information is pricing ($0.01/call, free quota), which is transactional, not behavioral.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is very concise (one sentence). It front-loads the purpose with '[NLP]' and includes pricing info which may be useful for cost-aware agents. However, the structure is minimal and could be improved with clearer separation of purpose and usage notes.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (one param, no output schema, no annotations), the description is minimal. It does not explain return values, typical use cases, or how it differs from similar NLP tools among siblings. The tool is simple, but more context would aid agent selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with one parameter 'text' described as '待分析文本'. The description does not add meaning beyond the schema, but as per guidelines, baseline is 3 for high coverage. No further elaboration on format or constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states '词法分析(分词+词性标注)' which clearly indicates lexical analysis (word segmentation and POS tagging). The '[NLP]' prefix groups it under NLP tasks. However, it does not explicitly distinguish from sibling tools like baidu_sentiment or baidu_keyword_extraction, though the specific task is clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. The description only states what it does but does not mention prerequisites, context, or when not to use it. Sibling tools like baidu_keyword_extraction or baidu_sentiment perform different NLP tasks, but no comparison is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wuzenghai616-lang/goldbean'
If you have feedback or need assistance with the MCP directory API, please join our Discord server