Skip to main content
Glama

delete_virtual_key

Destructive

Delete a virtual key by slug. This irreversible action removes the key and breaks any prompts or configs that reference it, so verify no active dependencies first.

Instructions

Delete a virtual key by slug. This is irreversible and will break prompts and configs that reference the slug, so confirm no active dependencies first. Returns success after removal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe slug of the virtual key to delete

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

  • The actual service handler that executes the delete logic. Calls this.delete() on /virtual-keys/{slug} via BaseService and returns success.
    async deleteVirtualKey(slug: string): Promise<{ success: boolean }> {
    	await this.delete(`/virtual-keys/${this.encodePathSegment(slug)}`);
    	return { success: true };
    }
  • Registration of the 'delete_virtual_key' tool on the MCP server, with description, schema reference, and handler that calls service.keys.deleteVirtualKey.
    // Phase 2: Delete virtual key tool
    server.tool(
    	"delete_virtual_key",
    	"Delete a virtual key by slug. This is irreversible and will break prompts and configs that reference the slug, so confirm no active dependencies first. Returns success after removal.",
    	KEYS_TOOL_SCHEMAS.deleteVirtualKey,
    	async (params) => {
    		const result = await service.keys.deleteVirtualKey(params.slug);
    		return {
    			content: [
    				{
    					type: "text",
    					text: JSON.stringify(
    						{
    							message: `Successfully deleted virtual key "${params.slug}"`,
    							success: result.success,
    						},
    						null,
    						2,
    					),
    				},
    			],
    		};
    	},
    );
  • Zod schema definition for deleteVirtualKey input - requires a 'slug' string parameter.
    deleteVirtualKey: {
    	slug: z.string().describe("The slug of the virtual key to delete"),
    },
  • Helper method encodePathSegment used by deleteVirtualKey to safely encode the slug in the URL path.
    protected encodePathSegment(value: string): string {
    	return encodeURIComponent(value);
    }
  • BaseService.delete method that issues the HTTP DELETE request to the API endpoint.
    protected async delete<T>(path: string): Promise<T> {
    	return this.executeRequest<T>("DELETE", path, { allowNoContent: true });
    }
Behavior5/5

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

Description adds valuable context beyond annotations (destructiveHint=true), explaining irreversible nature and secondary effects.

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, front-loaded with purpose, no extraneous content.

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?

Simple tool with one parameter, description covers purpose, side effects, and return value adequately.

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

Parameters3/5

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

Schema coverage is 100% with adequate description for the single parameter; description adds no additional meaning.

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 deletes a virtual key by slug, distinguishing it from sibling delete tools for other resources.

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 warns about irreversibility and impact on prompts/configs, advising to confirm no active dependencies first.

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