Skip to main content
Glama
bssth
by bssth

aspro_describe

Retrieves the full API schema for a REST operation by providing module, entity, and method. Returns HTTP method, path, parameters, and request-body fields with types and descriptions.

Instructions

Return the full schema for one operation: HTTP method, path, query/path parameters, request-body fields with types and descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moduleYes
entityYes
methodYesMethod segment, e.g. 'list', 'get', 'create', 'update', 'delete'.

Implementation Reference

  • The handler function for 'aspro_describe'. It calls spec.describe(module, entity, method) and returns the full operation schema (HTTP method, path, query/path parameters, request-body fields, etc.) or an error message if not found.
    async ({ module, entity, method }) => {
      const op = spec.describe(module, entity, method);
      if (!op) {
        return asJson({
          error: `No operation ${module}/${entity}/${method}. Use aspro_list_methods to discover.`,
        });
      }
      return asJson({
        module: op.module,
        entity: op.entity,
        method: op.method,
        httpMethod: op.httpMethod,
        path: op.path,
        description: op.description,
        tags: op.tags,
        parameters: op.parameters,
        bodyContentType: op.bodyContentType,
        bodyRequired: op.bodyRequired,
        bodyProperties: op.bodyProperties,
      });
    },
  • The Zod input schema for 'aspro_describe', defining module, entity, and method as required strings.
      inputSchema: {
        module: z.string(),
        entity: z.string(),
        method: z.string().describe("Method segment, e.g. 'list', 'get', 'create', 'update', 'delete'."),
      },
    },
  • src/index.ts:113-145 (registration)
    Registration of the 'aspro_describe' tool via server.registerTool(), binding name, description, schema, and handler together.
    server.registerTool(
      "aspro_describe",
      {
        description:
          "Return the full schema for one operation: HTTP method, path, query/path parameters, request-body fields with types and descriptions.",
        inputSchema: {
          module: z.string(),
          entity: z.string(),
          method: z.string().describe("Method segment, e.g. 'list', 'get', 'create', 'update', 'delete'."),
        },
      },
      async ({ module, entity, method }) => {
        const op = spec.describe(module, entity, method);
        if (!op) {
          return asJson({
            error: `No operation ${module}/${entity}/${method}. Use aspro_list_methods to discover.`,
          });
        }
        return asJson({
          module: op.module,
          entity: op.entity,
          method: op.method,
          httpMethod: op.httpMethod,
          path: op.path,
          description: op.description,
          tags: op.tags,
          parameters: op.parameters,
          bodyContentType: op.bodyContentType,
          bodyRequired: op.bodyRequired,
          bodyProperties: op.bodyProperties,
        });
      },
    );
  • The SpecIndex.describe() helper method that looks up an operation by module/entity/method key in the internal byKey map.
    describe(module: string, entity: string, method: string): OperationSpec | undefined {
      return this.byKey.get(this.makeKey(module, entity, method));
    }
Behavior2/5

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

No annotations provided, and the description only states it returns schema. It does not disclose whether the operation is read-only, any required permissions, or side effects. The agent is left to infer that it is a safe read operation.

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?

A single sentence that efficiently communicates the tool's purpose. It is front-loaded and avoids redundancy. Slightly more structure or enumeration could improve clarity.

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?

The description explains what the tool returns but lacks details on output format, which is not provided in an output schema. For a schema-description tool, it is acceptable but not exhaustive. No mention of error conditions or usage context.

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 input schema has 3 parameters, but only method has a description. The overall description adds context that the parameters identify a specific operation, partially compensating for low schema coverage (33%). However, module and entity remain unexplained.

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 returns the full schema for one operation, listing HTTP method, path, parameters, and request-body fields. It distinguishes from siblings like aspro_list_methods by specifying 'one operation'.

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 explicit guidance on when to use this tool versus alternatives like aspro_list_methods or aspro_search. The context of siblings implies differentiation, but the description does not state when to choose this tool.

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/bssth/aspro-mcp'

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