Skip to main content
Glama

list_virtual_keys

Read-onlyIdempotent

List virtual keys in your Portkey org to retrieve slugs for prompts or auditing. Returns name, slug, status, usage limits, rate limits, reset state, and model config.

Instructions

List provider API keys stored as virtual keys in your Portkey org. Use this to find slugs before wiring prompts/configs or auditing limits. Returns total plus name, slug, status, usage limits, rate limits, reset state, and model config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Implementation Reference

  • MCP tool handler for 'list_virtual_keys'. Calls service.keys.listVirtualKeys() and formats the response to include total count and an array of virtual keys with name, slug, status, note, usage_limits, rate_limits, reset_usage, created_at, and model_config.
    // List virtual keys tool
    server.tool(
    	"list_virtual_keys",
    	"List provider API keys stored as virtual keys in your Portkey org. Use this to find slugs before wiring prompts/configs or auditing limits. Returns total plus name, slug, status, usage limits, rate limits, reset state, and model config.",
    	KEYS_TOOL_SCHEMAS.listVirtualKeys,
    	async () => {
    		const virtualKeys = await service.keys.listVirtualKeys();
    		return {
    			content: [
    				{
    					type: "text",
    					text: JSON.stringify(
    						{
    							total: virtualKeys.total,
    							virtual_keys: virtualKeys.data.map((key) => ({
    								name: key.name,
    								slug: key.slug,
    								status: key.status,
    								note: key.note,
    								usage_limits: key.usage_limits
    									? {
    											credit_limit: key.usage_limits.credit_limit,
    											alert_threshold: key.usage_limits.alert_threshold,
    											periodic_reset: key.usage_limits.periodic_reset,
    										}
    									: null,
    								rate_limits:
    									key.rate_limits?.map((limit) => ({
    										type: limit.type,
    										unit: limit.unit,
    										value: limit.value,
    									})) ?? null,
    								reset_usage: key.reset_usage,
    								created_at: key.created_at,
    								model_config: key.model_config,
    							})),
    						},
    						null,
    						2,
    					),
    				},
    			],
    		};
    	},
    );
  • Input schema for list_virtual_keys tool — empty object (no parameters required).
    const KEYS_TOOL_SCHEMAS = {
    	listVirtualKeys: {},
  • Zod schema for the API response from GET /virtual-keys, validating the list response structure.
    export const ListVirtualKeysResponseSchema = z.object({
    	object: z.literal("list"),
    	total: z.number(),
    	data: z.array(VirtualKeySchema),
    });
  • Service method that makes the HTTP GET request to '/virtual-keys' to fetch virtual keys from the Portkey API.
    async listVirtualKeys(): Promise<ListVirtualKeysResponse> {
    	return this.get<ListVirtualKeysResponse>("/virtual-keys");
    }
  • TypeScript interface for the list virtual keys API response.
    export interface ListVirtualKeysResponse {
    	object: "list";
    	total: number;
    	data: VirtualKey[];
    }
Behavior4/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds value by specifying the return fields (total, name, slug, status, usage limits, rate limits, reset state, model config), which goes beyond annotations. No contradictions.

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 sentences that are front-loaded with the core purpose, followed by a usage hint and return summary. Every sentence adds value with no unnecessary words.

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 zero parameters, rich annotations, and an existing output schema, the description covers the tool's behavior, use context, and return structure. It is fully complete for an agent to understand when and how to use this 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?

No parameters in the input schema (schema coverage 100%), so no param details are needed. The description compensates by describing the output, making it clear what the tool returns without 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?

Clearly states it lists provider API keys stored as virtual keys in the Portkey org, and mentions use cases like finding slugs before wiring prompts/configs or auditing limits. Differentiates from sibling tools like get_virtual_key (single retrieval) and create_virtual_key.

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?

Provides explicit guidance: use to find slugs before wiring prompts/configs or auditing limits. While it doesn't explicitly say when not to use, the context and sibling tools make it clear this is for listing all keys, not for single key operations.

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/s-b-e-n-s-o-n/portkey-admin-mcp'

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