Skip to main content
Glama
kaminari-ad

@kaminari-ad/mcp

Official
by kaminari-ad

List Api Keys

list_api_keys
Read-onlyIdempotent

Retrieve your organization's API keys with details such as ID, key prefix, display name, expiry, and creation date. This endpoint provides key metadata without exposing the full secret.

Instructions

List the organization's API keys: id, key prefix (first 8 chars of the secret), display name, expiry, created_at. The full secret is NEVER returned by this endpoint — only the prefix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the list_api_keys tool logic. Calls ctx.api.listApiKeys() and returns the result with items and total count.
    handler: async (_input, ctx): Promise<Result<ListApiKeysOutput, ToolError>> => {
      const result = await ctx.api.listApiKeys();
      if (result.isErr()) return err(mapApiError(result.error));
      return ok({ items: result.value, total: result.value.length });
    },
  • Input shape (empty object) and output TypeScript interface (ListApiKeysOutput with items and total).
    const ListApiKeysInputShape = {} as const;
    type ListApiKeysInputShape = typeof ListApiKeysInputShape;
    
    export interface ListApiKeysOutput {
      readonly items: readonly ApiKeyResponse[];
      readonly total: number;
    }
  • Registration of listApiKeysTool in the central tool registry via register(listApiKeysTool).
    register(listApiKeysTool);
  • HTTP API gateway implementation that makes the actual GET /api/v1/account/api-keys call.
    async listApiKeys(): Promise<Result<readonly ApiKeyResponse[], ApiError>> {
      return call("GET", "/api/v1/account/api-keys", {}, parseApiKeyList);
  • Domain port interface defining the listApiKeys method contract.
    listApiKeys(): Promise<Result<readonly ApiKeyResponse[], ApiError>>;
Behavior4/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds a critical behavioral detail: the full secret is never returned, only the prefix. This goes beyond the annotations.

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, tightly written with no unnecessary words. It is front-loaded with the action and immediately lists outputs.

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?

Given the tool has no parameters and no output schema, the description is complete. It covers what the tool does, what it returns, and a critical behavioral note about the secret.

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 tool has no parameters, so schema coverage is 100%. The description mentions the fields returned, which adds context beyond the empty schema. Baseline for 0 parameters is 4.

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 that the tool lists the organization's API keys and specifies the fields returned (id, key prefix, display name, expiry, created_at). It distinguishes itself from sibling tools like create_api_key and revoke_api_key.

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?

While the purpose is clear, the description does not explicitly state when to use this tool versus alternatives. It implies usage for listing keys but lacks explicit when-to-use or when-not-to-use guidance.

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/kaminari-ad/mcp'

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