search_promptsSearch public InkRoom image prompts by up to three keyword groups to retrieve complete prompts, example image links, and provenance—no login or API key required.
Search public InkRoom image prompts using up to 3 keyword groups. Returns complete prompts, original example image links and provenance. No login or Key. A search error is not an empty result.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes |
Changes observed during successful MCP inspections.
v1.0.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: no authentication required, and the important caveat that a search error must not be treated as an empty result, which affects how the agent should handle failures.
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?
Three tight sentences with no filler: what it searches, what it returns, and the auth/error caveats. The key information is front-loaded.
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?
With no output schema, the description appropriately summarizes return content (complete prompts, example image links, provenance) and covers auth and error handling. The only gap is the undocumented limit parameter.
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 description coverage is 0%, so the description must compensate. It clarifies that query is composed of up to 3 keyword groups, which adds real meaning, but the limit parameter (default 3, range 1-5) is never explained in the description or schema.
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?
States a specific verb and resource ("Search public InkRoom image prompts"), plus scope ("up to 3 keyword groups") and what comes back. It is clearly distinguishable from siblings help, list_models, and optimize_prompt.
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?
Usage is implied by the name and by "No login or Key", and the note "A search error is not an empty result" tells the agent how to interpret failures. However, it never says when to choose this over a related tool like optimize_prompt, nor any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.