List all available prompts.
Returns JSON with prompt metadata including name, description, and optional arguments.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It does state the return format ('Returns JSON with prompt metadata'), which adds value, but it does not explicitly mention that the operation is read-only or discuss any side effects, authentication, or rate limits. Since 'List' inherently suggests a read operation, this is minimally acceptable.
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 concise and front-loaded with the primary action. The second sentence about return format adds necessary context without redundancy. Every word earns its place.
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 simplicity of the tool (zero parameters) and the existence of an output schema, the description is complete. It clearly states what the tool does and what it returns, and no additional behavioral details are essential for this straightforward list operation.
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 tool has zero parameters, so the schema coverage is trivially 100%. Per the rubric, a baseline of 4 is appropriate when there are no parameters to describe. The description does not need to add parameter information.
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 'List all available prompts' using a specific verb and resource. It distinguishes itself from the sibling tool 'get_prompt' by focusing on listing all prompts rather than retrieving a single one.
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 an agent needs to enumerate all prompts, but it does not explicitly mention when to use this tool over alternatives like 'get_prompt'. There are no exclusions provided, so it is adequate but not explicit.
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.
Each tool targets a distinct astrological function: reference lookups (sign, planet, house, aspect), chart calculations (birth_chart, planetary_positions), transit analysis (current_transits, transit_search), progression, calendar generation, and prompt management. Even similar tools like current_transits and transit_search are clearly differentiated by scope (current vs. period-based).
Naming is largely lowercase_snake_case but inconsistent in verb usage: get_* for reference lookups, while others are noun phrases (birth_chart, planetary_positions) or arbitrary verbs (generate_calendar_events). The pattern is readable but not uniform across the set.
12 tools is well within the ideal range for a domain-specific server. Each tool covers a distinct need without redundancy, and the count feels balanced for an astrology API.
The tool surface covers the core astrological workflow: reference data (signs, planets, houses, aspects), chart generation (birth, positions), transits, progressions, and calendar events. The inclusion of prompt tools also supports interpretation, leaving no obvious dead ends.