Retrieve all Oracle Cloud Infrastructure services with pricing categories, or filter by compute, storage, database, networking, Kubernetes, AI/ML, or observability.
List all OCI services with pricing categories. Filter by category: compute, storage, database, networking, kubernetes, ai-ml, observability, etc.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Filter by service category |
Changes observed during successful MCP inspections.
v1.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent behavior. The description adds no extra behavioral traits such as pagination or rate limits, so it does not enhance 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?
The description is a single sentence followed by examples, concise and front-loaded with the core action.
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 simple list tool with one optional parameter and no output schema, the description is complete enough; it provides the purpose and filtering capability.
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%, and the description provides example values for the category parameter, but does not add significant new meaning beyond the 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?
The description clearly states the tool lists OCI services with pricing categories and provides filtering by category, distinguishing it from siblings like list_services_by_category which doesn't mention pricing.
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 gives examples of filter categories but lacks explicit guidance on when to use this tool versus alternatives (e.g., specific service listers).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.