Skip to main content
Glama
bssth
by bssth

aspro_list_modules

List all top-level Aspro.Cloud API modules with entity and operation counts to discover available modules like CRM, fin, agile, task.

Instructions

List all top-level Aspro.Cloud API modules (crm, fin, agile, task, etc.) with entity and operation counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:43-51 (registration)
    Registration of the 'aspro_list_modules' tool via server.registerTool, with schema and handler that delegates to spec.listModules().
    server.registerTool(
      "aspro_list_modules",
      {
        description:
          "List all top-level Aspro.Cloud API modules (crm, fin, agile, task, etc.) with entity and operation counts.",
        inputSchema: {},
      },
      async () => asJson(spec.listModules()),
    );
  • Input schema for aspro_list_modules: description text, empty inputSchema (no parameters).
    {
      description:
        "List all top-level Aspro.Cloud API modules (crm, fin, agile, task, etc.) with entity and operation counts.",
      inputSchema: {},
  • Handler function: async () => asJson(spec.listModules()) — calls SpecIndex.listModules() and wraps result in JSON text content.
    async () => asJson(spec.listModules()),
  • SpecIndex.listModules() — iterates operations to count per module, returns sorted array of {module, entityCount, operationCount}.
    listModules(): { module: string; entityCount: number; operationCount: number }[] {
      const counts = new Map<string, number>();
      for (const op of this.operations) {
        counts.set(op.module, (counts.get(op.module) ?? 0) + 1);
      }
      return [...this.modules.entries()]
        .map(([module, entities]) => ({
          module,
          entityCount: entities.size,
          operationCount: counts.get(module) ?? 0,
        }))
        .sort((a, b) => a.module.localeCompare(b.module));
    }
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only states what the tool does (list modules with counts) but does not mention authentication needs, performance, data freshness, or what 'counts' refers to exactly. This is minimal disclosure.

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, clear sentence that conveys the tool's purpose succinctly with no wasted words. It is front-loaded and efficient.

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?

Given the tool has no parameters and no output schema, the description provides the essential purpose. However, it could mention the format of counts (e.g., numbers, objects) or any limitations. Overall, it is reasonably complete for a simple listing tool.

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

Parameters4/5

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

The input schema has no parameters, so baseline is 4. The description does not add parameter semantics because there are none to describe, which 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 uses a specific verb ('list') and resource ('top-level Aspro.Cloud API modules'), clearly stating the tool's function. It distinguishes itself from sibling tools like aspro_list_entities (which lists entities within a module) and aspro_list_methods (which lists operations).

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 for getting an overview of modules, but does not explicitly state when to use this tool versus alternatives (e.g., aspro_list_entities for deeper detail). No when-not or alternative guidance is provided.

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