Skip to main content
Glama
bssth
by bssth

aspro_list_methods

List HTTP operations for a specified module, optionally filtered by entity, to discover available API methods and their paths.

Instructions

List operations (HTTP method + path + short description) for a given module and optional entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moduleYesModule name.
entityNoEntity name. Omit to list operations across all entities of the module.

Implementation Reference

  • src/index.ts:73-95 (registration)
    Registration of the 'aspro_list_methods' tool via server.registerTool, with Zod input schema (module required, entity optional) and handler that calls spec.listMethods().
    server.registerTool(
      "aspro_list_methods",
      {
        description:
          "List operations (HTTP method + path + short description) for a given module and optional entity.",
        inputSchema: {
          module: z.string().describe("Module name."),
          entity: z
            .string()
            .optional()
            .describe("Entity name. Omit to list operations across all entities of the module."),
        },
      },
      async ({ module, entity }) => {
        const ops = spec.listMethods(module, entity);
        if (ops.length === 0) {
          return asJson({
            error: `No operations found for module="${module}"${entity ? `, entity="${entity}"` : ""}.`,
          });
        }
        return asJson({ count: ops.length, operations: ops.map(summarizeOp) });
      },
    );
  • Handler function for aspro_list_methods: calls spec.listMethods(module, entity), returns error if empty or a JSON summary of operations.
    async ({ module, entity }) => {
      const ops = spec.listMethods(module, entity);
      if (ops.length === 0) {
        return asJson({
          error: `No operations found for module="${module}"${entity ? `, entity="${entity}"` : ""}.`,
        });
      }
      return asJson({ count: ops.length, operations: ops.map(summarizeOp) });
    },
  • SpecIndex.listMethods() — the core helper that filters operations by module and optional entity, then sorts by entity and method.
    listMethods(module: string, entity?: string): OperationSpec[] {
      return this.operations
        .filter((o) => o.module === module && (entity ? o.entity === entity : true))
        .sort((a, b) =>
          a.entity.localeCompare(b.entity) || a.method.localeCompare(b.method),
        );
    }
  • OperationSpec interface — the type definition for each operation returned by listMethods.
    export interface OperationSpec {
      module: string;
      entity: string;
      method: string;
      path: string;
      httpMethod: HttpMethod;
      description?: string;
      tags: string[];
      parameters: ParameterSpec[];
      bodyContentType?: string;
      bodyProperties: BodyPropSpec[];
      bodyRequired: string[];
      responses: Record<string, unknown>;
    }
  • summarizeOp() helper used to map OperationSpec objects into a concise summary for the tool response.
    function summarizeOp(op: OperationSpec) {
      return {
        module: op.module,
        entity: op.entity,
        method: op.method,
        httpMethod: op.httpMethod,
        path: op.path,
        description: op.description,
      };
    }
Behavior2/5

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

No annotations provided, so the description carries full burden. It only states the output format (HTTP method + path + short description) but does not disclose any behavioral traits such as read-only nature, authentication requirements, rate limits, or potential side effects.

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?

The description is one sentence with 14 words, achieving conciseness. It is front-loaded with the main action and resource. However, it could be slightly more structured or include a brief usage example.

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 no output schema, the description partially explains the return format (HTTP method + path + short description). However, it lacks details on ordering, pagination, or possible errors. For a simple listing tool, it is minimally adequate but could be more informative.

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 both parameters described. The description adds no new semantic information beyond the schema; it essentially repeats the schema descriptions. Thus, baseline 3 is appropriate.

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 'List' and the resource 'operations (HTTP method + path + short description)'. It specifies that operations are listed for a given module and optional entity, which distinguishes it from siblings like 'aspro_list_entities' and 'aspro_list_modules'.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (to list methods for a module), but it does not explicitly state when to use this tool versus alternatives like 'aspro_search' or 'aspro_describe'. No guidance on prerequisites or context for using the optional entity parameter.

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