Lists OCI Governance services including Access Governance, Fleet Management, and License Manager, with optional filtering by governance service type.
[DEPRECATED: use list_services_by_category with category="governance"] List OCI Governance services including Access Governance, Fleet Management, and License Manager.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Filter by governance service type |
Changes observed during successful MCP inspections.
v1.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description states the tool lists services (read-only), which aligns with annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true). It adds the deprecation status, a key behavioral trait. 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 sentence containing deprecation notice, purpose, and example services. No wasted words, and the deprecation is front-loaded.
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 deprecated tool with a single optional parameter and strong annotations, the description is complete. It provides the necessary information to avoid misuse and guides users to the correct 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?
Schema coverage is 100%, with the 'type' parameter fully described via enum values. The description lists examples that match the enum values, adding minimal extra value. Baseline 3 is appropriate.
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 Governance services, provides examples (Access Governance, Fleet Management, License Manager), and includes a deprecation notice directing users to an alternative. The verb 'list' and resource 'governance services' are specific and unambiguous.
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?
Explicitly marks the tool as deprecated and instructs users to use list_services_by_category with category='governance' instead. This provides clear when-to-use and when-not-to-use guidance, referencing a specific sibling tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.