Skip to main content
Glama
konsulto

@konsulto/mcp

Official
by konsulto

konsulto_search_templates

Search the finding-template catalog using text and severity filters. Returns key fields to choose a template before composing a finding.

Instructions

Search the finding-template catalog. Returns a slim shape (id, title, severity, summary, slot names, taxonomy) — NOT the full template body. Use this to pick a template before calling konsulto_compose_finding. When multiple candidates match, prefer the one whose summary best fits the evidence in hand.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search across title and aliases.
severityNo
limitNo

Implementation Reference

  • Handler function for konsulto_search_templates. Calls GET /finding-templates with optional search query, severity filter, and limit. Returns slim template objects (id, title, severity, summary, slot names, taxonomy).
    async ({ q, severity, limit }) => {
      try {
        const params: Record<string, string> = {
          slim: '1',
          page: '1',
          limit: String(limit ?? 10),
        };
        if (q) params.search = q;
        if (severity) params.severity = severity;
        const data = (await client.get<any>('/finding-templates', { params })) as any;
        const items = data?.items ?? data?.data ?? data ?? [];
        return ok({ templates: items });
      } catch (err) {
        return errResult(err);
      }
    },
  • src/server.ts:249-279 (registration)
    Tool registration for konsulto_search_templates with description and Zod schema for parameters: q (optional string), severity (optional enum), limit (optional number 1-50, default 10).
    server.tool(
      'konsulto_search_templates',
      'Search the finding-template catalog. Returns a slim shape (id, title, ' +
        'severity, summary, slot names, taxonomy) — NOT the full template body. ' +
        'Use this to pick a template before calling konsulto_compose_finding. ' +
        'When multiple candidates match, prefer the one whose summary best fits ' +
        'the evidence in hand.',
      {
        q: z.string().optional().describe('Free-text search across title and aliases.'),
        severity: z
          .enum(['critical', 'high', 'medium', 'low', 'informative'])
          .optional(),
        limit: z.number().int().min(1).max(50).default(10).optional(),
      },
      async ({ q, severity, limit }) => {
        try {
          const params: Record<string, string> = {
            slim: '1',
            page: '1',
            limit: String(limit ?? 10),
          };
          if (q) params.search = q;
          if (severity) params.severity = severity;
          const data = (await client.get<any>('/finding-templates', { params })) as any;
          const items = data?.items ?? data?.data ?? data ?? [];
          return ok({ templates: items });
        } catch (err) {
          return errResult(err);
        }
      },
    );
  • Input schema for konsulto_search_templates: q (free-text search), severity (critical/high/medium/low/informative), limit (1-50, default 10).
    {
      q: z.string().optional().describe('Free-text search across title and aliases.'),
      severity: z
        .enum(['critical', 'high', 'medium', 'low', 'informative'])
        .optional(),
      limit: z.number().int().min(1).max(50).default(10).optional(),
    },
  • Helper function ok() used to format successful tool responses as JSON text content.
    function ok(payload: unknown) {
      return {
        content: [{ type: 'text' as const, text: JSON.stringify(payload, null, 2) }],
      };
    }
  • Helper function errResult() used to format error responses for tool handlers.
    function errResult(err: unknown) {
      const message = err instanceof Error ? err.message : String(err);
      return {
        isError: true,
        content: [{ type: 'text' as const, text: `Error: ${message}` }],
      };
    }
Behavior4/5

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

No annotations provided, so description carries full burden. Clearly states returns slim shape and does not return full body. Implies read-only behavior. Minor gaps on search behavior (case sensitivity, pagination) but core transparency is strong.

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?

Three sentences, front-loaded with purpose. Every sentence adds value without redundancy.

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?

Covers workflow role, return shape, and selection heuristic. Missing parameter usage context but otherwise complete for agent decision-making.

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

Parameters2/5

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

Does not mention any of the three parameters (q, severity, limit). Schema coverage is only 33% (q described), but description adds no parameter guidance. Should compensate for low coverage.

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?

States a specific verb 'Search' and resource 'finding-template catalog'. Clearly distinguishes from sibling konsulto_compose_finding by positioning itself as a precursor step.

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

Usage Guidelines5/5

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

Explicitly says 'Use this to pick a template before calling konsulto_compose_finding' and provides selection heuristic. Names the specific sibling tool as follow-up.

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/konsulto/konsulto-mcp'

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