Skip to main content
Glama
git-scarrow

Oracle MCP Server

by git-scarrow

list_schemas

Retrieve all database schemas to enable SQL queries and database introspection across Oracle databases.

Instructions

List all schemas in the database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_schemas' tool. It executes a SQL query against the ALL_USERS view to retrieve distinct schema names, their creation dates, and classifies them as SYSTEM or USER schemas, then returns the results as formatted JSON.
    async handleListSchemas(args) {
      const query = `
        SELECT DISTINCT 
          username AS schema_name,
          created,
          CASE 
            WHEN username IN ('SYS', 'SYSTEM', 'DBSNMP', 'SYSMAN') THEN 'SYSTEM'
            ELSE 'USER'
          END AS schema_type
        FROM all_users
        ORDER BY username
      `;
      
      const result = await this.executeQuery(query);
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result.rows, null, 2)
          }
        ]
      };
    }
  • src/index.js:265-272 (registration)
    Registration of the 'list_schemas' tool in the ListToolsRequestHandler, including its name, description, and input schema (empty object since no parameters required).
    {
      name: 'list_schemas',
      description: 'List all schemas in the database',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    }
  • Input schema definition for the 'list_schemas' tool, specifying an empty object as no input parameters are required.
    inputSchema: {
      type: 'object',
      properties: {}
    }
  • Dispatch case in the CallToolRequestHandler that routes 'list_schemas' calls to the handleListSchemas method.
    case 'list_schemas':
      return await this.handleListSchemas(args);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool lists schemas but doesn't describe what 'list' entails—whether it returns names only, full metadata, pagination behavior, permission requirements, or potential side effects. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a zero-parameter tool and front-loads the essential information.

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 zero-parameter tool with no output schema, the description is minimally adequate but lacks depth. It doesn't explain what 'list' returns (e.g., schema names, metadata, format) or how it differs from sibling tools. Given the simplicity of the tool, the description meets basic needs but could be more informative.

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

Parameters4/5

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

The tool has zero parameters, and schema description coverage is 100% (since there are no parameters to document). The description appropriately doesn't discuss parameters, which aligns with the empty input schema. No additional parameter semantics are needed or provided.

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 action ('List') and target resource ('all schemas in the database'), making the tool's purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_tables' or 'describe_table', which would require mentioning that this tool returns schema-level metadata rather than table-level information.

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

Usage Guidelines2/5

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 like 'list_tables' or 'describe_table'. There's no mention of prerequisites, context for usage, or comparisons to sibling tools, leaving the agent to infer appropriate usage scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/git-scarrow/oracle-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server