get_pricingCurrent Sparks Scribe plans and pricing in Australian dollars (GST inclusive), including annual pricing and the refund policy.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations disclose readOnly and idempotent. Description adds details on currency (AUD, GST inclusive) and inclusion of refund policy and annual pricing, enhancing understanding beyond annotations.
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?
Single sentence with all key information: plans, pricing, currency, refund policy. Front-loaded and efficient.
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?
No output schema, but description covers expected returns (plans, pricing, annual pricing, refund policy). Adequate for a simple pricing tool.
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?
No parameters exist (0 params, schema coverage 100%), so baseline 4 applies. Description adds no param info since none needed.
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 clearly states the tool returns 'plans and pricing' with currency and GST detail. Distinguishes from sibling tools like 'about_sparks_scribe' and 'get_trial_info'.
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 explicit guidance on when to use vs. alternatives. The context implies pricing queries, but lacks 'when not to use' or mention of sibling tools.
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 has a clearly distinct purpose: about describes the app, example provides a sample note, pricing gives cost info, trial explains the trial. No overlap.
All tool names follow a consistent pattern: descriptive noun phrases with underscores (about_sparks_scribe, example_shift_note, get_pricing, get_trial_info).
With 4 tools, the server is well-scoped for an informational resource about Sparks Scribe. Each tool addresses a key user need without being too sparse or excessive.
The tool surface covers the main informational needs: definition, example, pricing, and trial. A minor gap is the lack of a tool for support or FAQ, but the core functionality is complete.