List OCI database options, including Autonomous, MySQL, PostgreSQL, and NoSQL, with pricing; filter by database type or license type to compare costs.
List all OCI database options (Autonomous, MySQL, PostgreSQL, NoSQL) with pricing.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Filter by database type | |
| licenseType | No | Filter by license type |
Changes observed during successful MCP inspections.
v1.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering safety and idempotency. The description adds minimal extra behavioral context (e.g., that it includes pricing). No contradictions.
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, clear sentence conveying all essential information. No fluff or unnecessary words.
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?
For a read-only list tool with two optional parameters and no output schema, the description is fairly complete. It specifies the content (database options and pricing). Minor gap: no mention of result format or pagination, but typical for such tools.
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 descriptive enum values for both parameters. The description adds no additional parameter semantics beyond 'with pricing', which is generic. Baseline score of 3 applies as schema does the heavy lifting.
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 explicitly states the action ('list'), the resource ('all OCI database options'), and key context ('with pricing'). It clearly defines scope by naming specific database types in parentheses. This distinguishes it from sibling tools like list_kubernetes_options.
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 is provided on when to use this tool versus alternatives such as compare_database_options or get_pricing. Lacks any when-not-to-use or prerequisite information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.