Skip to main content
Glama
l0kifs

project-explorer-mcp

by l0kifs

openapi_get_operation_details

Retrieve OpenAPI operation details by operationId, method+path, or path. Optionally resolve refs and format as JSON or Markdown.

Instructions

Get detailed information for specific OpenAPI operations.

Agent usage guidelines: - Use this tool when you need detailed information about specific API operations. - Use selectors to target specific operations by operationId, method+path, or path. - Set expand_refs=True to resolve schema references for full schema details. - Choose format_output="json" for structured data, "markdown" for formatted output.

Path requirements: - The path must not contain URL-encoding (e.g., '%'). - The path must be absolute. - The path must exist on disk and be a valid OpenAPI JSON or YAML file.

Args: spec_path (str): Absolute path to the OpenAPI JSON or YAML file. selectors (list[str]): List of selectors. Each selector can be: - operationId (exact match) - "METHOD /path" (e.g. "GET /users/{id}") - just a path (e.g. "/users/{id}") to match all methods on that path expand_refs (bool): Whether to resolve local $ref references in schemas. Defaults to False. format_output (str | None): Output format ('json' or 'markdown'). Defaults to server setting.

Returns: dict | str: For format_output="json": Dictionary containing operation details and metadata. - details: list of detailed operation records - count: number of matching operations - error: error message if any, None otherwise For format_output="markdown": formatted markdown string

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorsYes
spec_pathYes
expand_refsNo
format_outputNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses important behavioral traits: path must be absolute, unencoded, exist, and be a valid OpenAPI file; expand_refs behavior for resolving refs; format_output options; and return structure including error handling. This is more than enough for a read-only file inspection tool, though it does not elaborate on edge cases like empty results or permission issues.

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 well-structured with clear sections: purpose, usage guidelines, path requirements, args, returns. It is substantial yet every sentence provides necessary information for correct use. The front-loaded purpose and usage guidelines make it easy to scan, and the detailed parameter explanations are justified given the tool's complexity.

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

Completeness5/5

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

The description covers all essential aspects: what it does, when to use it, path constraints, parameter semantics, and return format (including error field). Despite having an output schema, the description still fully explains the return values and error handling, making it self-contained. No important context for selecting or invoking this tool is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It does so comprehensively: spec_path is defined as the absolute path, selectors are explained with examples, expand_refs has a clear default and effect, and format_output options are listed. This adds significant meaning beyond the raw schema, which only lists types and defaults.

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 the tool's purpose: 'Get detailed information for specific OpenAPI operations.' This is a specific verb+resource pair that distinguishes it from siblings like openapi_list_operations, which presumably lists operations. The mention of selectors (operationId, method+path, path) further clarifies its targeting of specific operations.

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 'Agent usage guidelines' section explicitly states when to use the tool: 'Use this tool when you need detailed information about specific API operations.' It explains how to use selectors and adjust expand_refs/format_output. However, it does not explicitly mention when not to use it or directly contrast with sibling tools like openapi_list_operations, so it lacks exclusions or alternatives.

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/l0kifs/project-explorer-mcp'

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