Skip to main content
Glama
Sign In
OCI MCP Server

OCI MCP Server

by sarthak-pansare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

find_resources

Search and query all Oracle Cloud Infrastructure resources using natural language. Filter by type, name, or lifecycle state with limit options.

Instructions

Search ALL OCI resources. Examples: 'query all resources where displayName =~ "web*"' 'query instance resources' 'query vcn,subnet resources where lifecycleState = "AVAILABLE"'

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": {
      "query": "<query>"
    },
    "name": "find_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose important behavioral traits such as pagination, rate limits, or error handling for invalid queries.

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 concise, front-loaded with the core purpose, and uses examples efficiently without 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?

Given only two parameters and no output schema, the description covers the query usage adequately but lacks details on output format, error scenarios, and limit parameter semantics.

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

Parameters3/5

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

The schema has no descriptions, but the description adds value by showing query syntax examples. However, it does not explain the 'limit' parameter or its default behavior.

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

Purpose5/5

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

The description clearly states it searches ALL OCI resources and provides specific query examples, making the purpose distinct from sibling tools that focus on individual resource types.

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

Usage Guidelines4/5

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

The description implies usage for cross-resource queries with examples, but does not explicitly state when to prefer other list tools over this general search.

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