Skip to main content
Glama
ActaLumen

@actalumen/mcp-server

Official
by ActaLumen

list_templates

Retrieve available compliance templates like SOC2 or GDPR to obtain the templateId needed for document verification.

Instructions

List compliance criteria templates available to the organization (e.g., 'SOC2 Vendor', 'GDPR DPA'). Call this before start_verification to find the right templateId. Each template encodes a checklist of criteria a document is verified against.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool's handler function executes the actual logic: it calls client.get('/v1/templates') to list available compliance criteria templates.
    export const listTemplates = defineTool({
      name: "list_templates",
      description:
        "List compliance criteria templates available to the organization (e.g., 'SOC2 Vendor', 'GDPR DPA'). Call this before start_verification to find the right templateId. Each template encodes a checklist of criteria a document is verified against.",
      inputSchema: Input,
      handler: async (_input, { client }) => client.get("/v1/templates"),
    });
  • Input schema: an empty object since list_templates takes no arguments.
    const Input = z.object({}).describe("No arguments.");
  • Registration: listTemplates is exported in the tools array, making it available as a tool.
    export const tools: ToolDef[] = [
      uploadDocument,
      getDocument,
      listDocuments,
      listTemplates,
      startVerification,
      getVerification,
      chatWithDocument,
      getUsage,
    ];
  • The defineTool helper wraps the tool definition into a typed ToolDef object.
    export const listTemplates = defineTool({
      name: "list_templates",
      description:
        "List compliance criteria templates available to the organization (e.g., 'SOC2 Vendor', 'GDPR DPA'). Call this before start_verification to find the right templateId. Each template encodes a checklist of criteria a document is verified against.",
      inputSchema: Input,
      handler: async (_input, { client }) => client.get("/v1/templates"),
    });
  • The defineTool helper function used to create type-safe tool definitions.
    export function defineTool<Input extends z.ZodTypeAny>(t: {
      name: string;
      description: string;
      inputSchema: Input;
      handler: (input: z.infer<Input>, ctx: ToolContext) => Promise<unknown>;
    }): ToolDef {
      return t as unknown as ToolDef;
    }
Behavior4/5

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

Although no annotations are provided, the description adequately conveys that this is a read-only listing operation. It does not discuss edge cases or failure modes, but for a simple list tool, this is sufficient.

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 two sentences, front-loaded with the core purpose, and includes a practical usage hint. Every sentence is informative and non-redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without an output schema, the description explains the return value (list of templates), gives examples, and describes what each template contains. It also provides integration context with start_verification, making it fully complete for an agent.

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?

There are zero parameters, and the schema description coverage is 100% stating 'No arguments.' The description adds value by explaining the return content and usage, meeting the baseline for no parameters.

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 lists compliance criteria templates, provides concrete examples ('SOC2 Vendor', 'GDPR DPA'), and explains their purpose for verification. It distinguishes itself from siblings like start_verification by explicitly calling it a prerequisite.

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?

The description explicitly advises to call this before start_verification to find the right templateId, providing clear when-to-use guidance. No exclusion is needed as no other sibling lists templates.

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/ActaLumen/mcp-server'

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