Skip to main content
Glama
code-alchemist01

Development Tools MCP Server

extract_api_schema

Extract API schema from discovered endpoints to document and analyze web service interfaces for development workflows.

Instructions

Extract API schema from discovered endpoints

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to analyze
endpointNoSpecific endpoint to extract schema from

Implementation Reference

  • Registration of the 'extract_api_schema' tool in the apiDiscoveryTools array, including name, description, and input schema definition.
    {
      name: 'extract_api_schema',
      description: 'Extract API schema from discovered endpoints',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'URL to analyze',
          },
          endpoint: {
            type: 'string',
            description: 'Specific endpoint to extract schema from',
          },
        },
        required: ['url'],
      },
    },
  • Input schema definition for the 'extract_api_schema' tool.
    inputSchema: {
      type: 'object',
      properties: {
        url: {
          type: 'string',
          description: 'URL to analyze',
        },
        endpoint: {
          type: 'string',
          description: 'Specific endpoint to extract schema from',
        },
      },
      required: ['url'],
    },
  • Handler logic in handleAPIDiscoveryTool function that processes the tool call by extracting URL/endpoint params and delegating to APIScraper.extractAPISchema.
    case 'extract_api_schema': {
      const url = params.url as string;
      const endpoint = params.endpoint as string | undefined;
      const schema = await apiScraper.extractAPISchema(url, endpoint);
      return schema;
    }
  • Core implementation of API schema extraction in APIScraper class, which discovers endpoints and constructs a schema object.
    async extractAPISchema(url: string, _endpoint?: string): Promise<Record<string, unknown>> {
      // This is a simplified version. In production, would analyze actual API responses
      const result = await this.discoverAPIEndpoints(url);
      
      const schema: Record<string, unknown> = {
        baseUrl: result.baseUrl,
        endpoints: result.endpoints.map((e) => ({
          method: e.method,
          path: e.path,
          parameters: e.parameters,
        })),
      };
    
      return schema;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It doesn't disclose whether this is a read-only operation, what permissions are needed, how it handles errors, or the format of extracted schema. This leaves critical behavioral traits unspecified.

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 with no wasted words, clearly front-loading the core purpose. It's appropriately sized for a tool with two parameters and no complex output schema.

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 the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is minimally adequate but incomplete. It lacks details on behavioral traits and usage context, though the schema covers parameters well, resulting in a baseline score.

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 description coverage is 100%, so parameters are well-documented in the schema. The description adds no additional meaning beyond implying 'url' and 'endpoint' relate to API schema extraction, aligning with the baseline for high schema coverage without extra param details.

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 ('extract') and resource ('API schema from discovered endpoints'), making the tool's purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'discover_api_endpoints' or 'test_api_endpoint', which prevents a perfect score.

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 such as 'discover_api_endpoints' or 'test_api_endpoint'. It lacks context about prerequisites (e.g., needing discovered endpoints first) or exclusions, leaving usage ambiguous.

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/code-alchemist01/development-tools-mcp-Server'

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