Skip to main content
Glama
bssth
by bssth

aspro_search

Search for modules, entities, methods by substring in name, path, description, or tags. Find what you need without knowing the exact name.

Instructions

Substring search across module/entity/method/path/description/tags. Useful when you don't know the exact module or entity name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSubstring to search for, case-insensitive.
limitNoMax results (default 30).

Implementation Reference

  • Tool registration and handler for 'aspro_search'. Calls spec.search() with the provided query and optional limit, then returns results as JSON.
    server.registerTool(
      "aspro_search",
      {
        description:
          "Substring search across module/entity/method/path/description/tags. Useful when you don't know the exact module or entity name.",
        inputSchema: {
          query: z.string().min(1).describe("Substring to search for, case-insensitive."),
          limit: z.number().int().positive().max(200).optional().describe("Max results (default 30)."),
        },
      },
      async ({ query, limit }) => {
        const ops = spec.search(query, limit ?? 30);
        return asJson({ count: ops.length, operations: ops.map(summarizeOp) });
      },
    );
  • Input schema for aspro_search: requires a 'query' string (min length 1) and an optional 'limit' integer (positive, max 200, default 30).
    inputSchema: {
      query: z.string().min(1).describe("Substring to search for, case-insensitive."),
      limit: z.number().int().positive().max(200).optional().describe("Max results (default 30)."),
    },
  • src/index.ts:97-111 (registration)
    Tool registered with the MCP server under the name 'aspro_search'.
    server.registerTool(
      "aspro_search",
      {
        description:
          "Substring search across module/entity/method/path/description/tags. Useful when you don't know the exact module or entity name.",
        inputSchema: {
          query: z.string().min(1).describe("Substring to search for, case-insensitive."),
          limit: z.number().int().positive().max(200).optional().describe("Max results (default 30)."),
        },
      },
      async ({ query, limit }) => {
        const ops = spec.search(query, limit ?? 30);
        return asJson({ count: ops.length, operations: ops.map(summarizeOp) });
      },
    );
  • The search() method on SpecIndex class performs a case-insensitive substring search across module, entity, method, path, description, and tags of all operations. Results are sorted by index position and limited.
    search(query: string, limit = 30): OperationSpec[] {
      const q = query.toLowerCase().trim();
      if (!q) return [];
      const results: { score: number; op: OperationSpec }[] = [];
      for (const op of this.operations) {
        const haystack = [
          op.module,
          op.entity,
          op.method,
          op.path,
          op.description ?? "",
          op.tags.join(" "),
        ]
          .join(" ")
          .toLowerCase();
        const idx = haystack.indexOf(q);
        if (idx >= 0) results.push({ score: idx, op });
      }
      results.sort((a, b) => a.score - b.score);
      return results.slice(0, limit).map((r) => r.op);
    }
Behavior3/5

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

With no annotations, the description carries the full burden. It states it performs substring search but offers no additional behavioral context (e.g., result limits, performance implications) beyond what the schema already provides.

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?

Two efficient sentences: the first defines purpose, the second provides usage guidance. No redundant 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?

The description sufficiently explains the tool's function and when to use it, given the simplicity of the tool (2 params, no output schema). It could briefly mention return format, but is largely complete.

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?

Schema coverage is 100%, baseline 3. The description adds value by specifying the search scope (module/entity/method/path/description/tags) beyond the schema's parameter descriptions.

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 it performs 'substring search across module/entity/method/path/description/tags' and distinguishes from siblings by noting its usefulness when the exact name is unknown.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use this tool ('when you don't know the exact module or entity name'), but does not explicitly name alternatives or exclusions.

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