Skip to main content
Glama

getSpecDefinition

Retrieve the complete contents of an API specification's definition using its spec ID.

Instructions

Gets the complete contents of an API spec's definition.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
specIdYesSpec ID

Implementation Reference

  • The GetSpecDefinitionTool class is the handler for the getSpecDefinition tool. It defines the class, schema, and execution logic. The run_tool method makes a GET request to /apis/{specId}/definition to retrieve the complete definition of an API specification.
    class GetSpecDefinitionTool(ToolHandler):
        """Get spec definition contents"""
        
        def __init__(self):
            super().__init__("getSpecDefinition")
        
        def get_tool_description(self) -> Tool:
            return Tool(
                name=self.name,
                description="Gets the complete contents of an API spec's definition.",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "specId": {
                            "type": "string",
                            "description": "Spec ID"
                        }
                    },
                    "required": ["specId"]
                },
            )
        
        async def run_tool(self, args: dict) -> list[TextContent]:
            spec_id = args["specId"]
            result = await postman_api_call("GET", f"/apis/{spec_id}/definition")
            return [TextContent(type="text", text=json.dumps(result, indent=2))]
  • Input schema for getSpecDefinition: requires a 'specId' (string) property describing the specification ID.
    def get_tool_description(self) -> Tool:
        return Tool(
            name=self.name,
            description="Gets the complete contents of an API spec's definition.",
            inputSchema={
                "type": "object",
                "properties": {
                    "specId": {
                        "type": "string",
                        "description": "Spec ID"
                    }
                },
                "required": ["specId"]
            },
        )
  • Registration of GetSpecDefinitionTool() in the register_all_tools function (line 1869) which returns all tool handler instances.
        GetSpecDefinitionTool(),
        CreateSpecFileTool(),
        GetSpecFilesTool(),
        GetSpecFileTool(),
        UpdateSpecFileTool(),
        
        # Spec-Collection Integration
        GenerateCollectionTool(),
        GetSpecCollectionsTool(),
        GenerateSpecFromCollectionTool(),
        GetGeneratedCollectionSpecsTool(),
        SyncCollectionWithSpecTool(),
        SyncSpecWithCollectionTool(),
        
        # Workspaces
        CreateWorkspaceTool(),
        GetWorkspaceTool(),
        GetWorkspacesTool(),
        UpdateWorkspaceTool(),
        
        # Other
        GetTaggedEntitiesTool(),
        RunCollectionTool(),
    ]
  • Test file references getSpecDefinition as one of the expected tool names in test_tool_names() to verify it is registered.
    "getSpecDefinition",
  • ToolHandler is the abstract base class that GetSpecDefinitionTool extends. It provides the __init__ (sets self.name), abstract get_tool_description(), and abstract run_tool() methods.
    class ToolHandler(ABC):
        """Base class for all Postman tool handlers"""
        
        def __init__(self, name: str):
            self.name = name
        
        @abstractmethod
        def get_tool_description(self) -> Tool:
            """Return the MCP Tool description for this handler"""
            pass
        
        @abstractmethod
        async def run_tool(self, arguments: dict) -> list[TextContent | ImageContent | EmbeddedResource]:
            """Execute the tool with the given arguments"""
            pass
Behavior2/5

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

With no annotations, the description should disclose behavioral traits (e.g., return size, permissions), but it only states it 'gets' contents, lacking depth.

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

Conciseness4/5

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

One concise sentence with no waste, but lacks additional structured information.

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

Completeness4/5

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

For a simple retrieval tool with one required parameter and no output schema, the description is mostly complete, though could note what 'complete contents' entails.

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?

Schema coverage is 100% with parameter specId already described, so the description adds no extra meaning; baseline 3 applies.

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 verb 'Gets' and the resource 'complete contents of an API spec's definition', which is specific and distinct from sibling tools like 'getSpec' or 'getSpecFile'.

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?

No guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites.

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/Sourav4670/postman-mcp'

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