Skip to main content
Glama
Sign In
OCI MCP Server

OCI MCP Server

by sarthak-pansare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_keys

Retrieve a list of keys in a vault by providing the compartment ID and the vault's management endpoint.

Instructions

List keys in a vault. Get management_endpoint from get_vault.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "compartment_id": "<compartment_id>",
      "management_endpoint": "<management_endpoint>"
    },
    "name": "list_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
compartment_idYes
management_endpointYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, and the description only states it lists keys. It does not disclose pagination, error behavior, or any other operational details expected for a list operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with two sentences, front-loading the main purpose. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool without output schema, the description covers the core action and a prerequisite. However, it lacks information about the output format, pagination behavior, or error conditions, making it moderately complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description only explains the management_endpoint parameter's source. compartment_id and limit lack any explanation, leaving the agent with only the schema titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists keys in a vault and directs to get management endpoint via get_vault. However, it does not differentiate from numerous sibling list tools, but the name and core purpose are clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a prerequisite (get management endpoint from get_vault) but no guidance on when to use this tool versus alternatives or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools