search_adviceSearch for advice by keyword or phrase (e.g., "confidence", "relationships"). Returns matching advice slips with text and IDs.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Keyword or phrase to search for within advice text. |
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The search query that was used | |
| slips | Yes | Array of matching advice slips | |
| total_results | Yes | Total number of matching advice slips |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "query": {
+ "description": "The search query that was used",
+ "type": "string"
+ },
+ "slips": {
+ "description": "Array of matching advice slips",
+ "items": {
+ "properties": {
+ "advice": {
+ "description": "The advice text",
+ "type": "string"
+ },
+ "id": {
+ "description": "Numeric ID of the advice slip",
+ "type": "number"
+ }
+ },
+ "required": [
+ "id",
+ "advice"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "total_results": {
+ "description": "Total number of matching advice slips",
+ "type": "number"
+ }
+ },
+ "required": [
+ "total_results",
+ "query",
+ "slips"
+ ],
+ "type": "object"
+}Input schema / examplesAdded value: +[
+ {
+ "query": "confidence"
+ },
+ {
+ "query": "relationships"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to disclose safety. It adds the return format (text and IDs) and the matching behavior, which is useful context, but it does not describe search nuances like ranking or filtering.
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?
The description is a single sentence, front-loaded with the verb, and provides essential information without fluff. Every word serves a purpose.
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 tool's simplicity (one parameter, output schema available, strong annotations), the description is sufficient for an agent to invoke it correctly. It defines the search input and the expected output shape.
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?
The single parameter 'query' has 100% schema description coverage, and the description repeats the same semantics ('keyword or phrase', 'within advice text'). The schema already defines it, so the description adds no additional meaning.
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?
The description clearly states the tool's function with a specific verb ('search'), the resource ('advice'), and the output ('matching advice slips with text and IDs'). This distinguishes it from sibling tools like get_advice or random_advice, which have different retrieval patterns.
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?
The description implies usage when a user needs to find advice by keyword, but it does not explicitly mention when to prefer this over get_advice or random_advice. There is no exclusion or alternative guidance, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.