Skip to main content
Glama

app_configuration_kv_delete

Remove key-value pairs from Azure App Configuration to manage application settings and maintain clean configuration stores.

Instructions

Delete a key-value from Azure App Configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesThe key to delete
labelNoThe label of the key-value to delete (optional)

Implementation Reference

  • Handler logic for app_configuration_kv_delete: deletes the key-value using AzureAppConfigurationClient.delete_configuration_setting and formats the response.
    elif name == "app_configuration_kv_delete":
        # Delete a key-value
        result = app_config_client.delete_configuration_setting(
            key=arguments["key"],
            label=arguments.get("label", None)
        )
        
        if result:
            response = {
                "key": result.key,
                "label": result.label,
                "deleted": True
            }
        else:
            response = {
                "key": arguments["key"],
                "label": arguments.get("label", None),
                "deleted": False,
                "message": "Key not found"
            }
  • Input schema definition for the app_configuration_kv_delete tool, specifying parameters key (required) and label (optional).
    Tool(
        name="app_configuration_kv_delete",
        description="Delete a key-value from Azure App Configuration",
        inputSchema={
            "type": "object",
            "properties": {
                "key": {
                    "type": "string",
                    "description": "The key to delete",
                },
                "label": {
                    "type": "string",
                    "description": "The label of the key-value to delete (optional)",
                },
            },
            "required": ["key"],
        },
    ),
  • Tool registration via the list_tools handler, which returns get_azure_tools() including the app_configuration_kv_delete tool.
    @server.list_tools()
    async def list_tools() -> list[Tool]:
        """List available Azure tools"""
        logger.debug("Handling list_tools request")
        return get_azure_tools()  # Use get_azure_tools
  • Dispatch registration in call_tool that routes app_configuration_kv_delete to the specific handler function.
    elif name.startswith("app_configuration_"):
        return await handle_app_configuration_operations(
            azure_rm, name, arguments
        )  # Use app configuration handler
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't specify whether this operation is reversible, requires specific permissions, has side effects (e.g., affecting other configurations), or what happens on success/failure. This is a significant gap for a mutation tool with zero annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the tool's complexity (a destructive operation with no output schema and no annotations), the description is incomplete. It lacks crucial details like behavioral traits (e.g., idempotency, error handling), usage context relative to siblings, and expected outcomes, which are essential for safe and effective tool invocation.

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?

The input schema has 100% description coverage, clearly documenting both parameters ('key' and optional 'label'). The description doesn't add any additional meaning beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete') and the resource ('a key-value from Azure App Configuration'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'app_configuration_kv_write' or 'blob_delete', which would require more specific context about Azure App Configuration vs. other services.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing the key to exist), exclusions, or comparisons to siblings like 'app_configuration_kv_read' or 'app_configuration_kv_write', leaving the agent to infer usage from the tool name alone.

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/mashriram/azure_mcp_server'

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