Retrieve detailed pricing and configuration options for a specific Oracle Cloud compute shape by specifying its family name, such as VM.Standard.E5.Flex.
Get detailed pricing and configuration options for a specific compute shape.
| Name | Required | Description | Default |
|---|---|---|---|
| shapeFamily | Yes | Shape family (e.g., VM.Standard.E5.Flex) |
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=true, destructiveHint=false, and idempotentHint=true, so the description adds minimal behavioral context beyond stating it gets data. No contradictions, but no extra disclosure like authorization needs or response details.
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, clear sentence that is front-loaded with the purpose. It contains no redundant information.
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?
While there is no output schema, the tool is simple with one parameter. The description is sufficient to understand input and high-level output (pricing and configuration), but could briefly mention the format of returned data.
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?
Input schema coverage is 100% for the single required parameter 'shapeFamily', which already has a descriptive example. The description does not add further meaning about parameter formatting or constraints 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 gets detailed pricing and configuration for a specific compute shape, using a specific verb and resource. It distinguishes from sibling tools like list_compute_shapes (which lists all shapes) and compare_compute_shapes (which compares shapes).
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 provides no guidance on when to use this tool versus alternatives, such as list_compute_shapes or compare_compute_shapes. It does not mention exclusions or context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.