Skip to main content
Glama

app_configuration_kv_read

Retrieve key-value pairs from Azure App Configuration to access application settings and feature flags for dynamic configuration management.

Instructions

Read key-values from Azure App Configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoThe key to read (optional, use * for wildcards, e.g. 'app1/*')
labelNoThe label filter (optional, use '\0' for no label, '*' for any label)

Implementation Reference

  • Core execution logic for the app_configuration_kv_read tool: retrieves Azure App Configuration key-values with optional key/label filters, formats them into a list of dicts, and sets response.
    if name == "app_configuration_kv_read":
        # Get key and label from arguments, both optional
        key = arguments.get("key", None)
        label = arguments.get("label", None)
        
        # List key-values with optional filtering by key and label
        if key:
            settings = list(app_config_client.list_configuration_settings(
                key_filter=key,
                label_filter=label
            ))
        else:
            settings = list(app_config_client.list_configuration_settings(
                label_filter=label
            ))
        
        # Format results for display
        result = []
        for setting in settings:
            result.append({
                "key": setting.key,
                "value": setting.value,
                "content_type": setting.content_type,
                "label": setting.label,
                "last_modified": setting.last_modified.isoformat() if setting.last_modified else None,
                "read_only": setting.read_only
            })
        response = {"settings": result}
  • Input schema definition for the app_configuration_kv_read tool, defining optional 'key' and 'label' parameters.
    Tool(
        name="app_configuration_kv_read",
        description="Read key-values from Azure App Configuration",
        inputSchema={
            "type": "object",
            "properties": {
                "key": {
                    "type": "string",
                    "description": "The key to read (optional, use * for wildcards, e.g. 'app1/*')",
                },
                "label": {
                    "type": "string",
                    "description": "The label filter (optional, use '\\0' for no label, '*' for any label)",
                },
            },
            "required": [],
        },
  • Tool registration in get_app_configuration_tools(), which is included in the server's list_tools() response.
    Tool(
        name="app_configuration_kv_read",
        description="Read key-values from Azure App Configuration",
        inputSchema={
            "type": "object",
            "properties": {
                "key": {
                    "type": "string",
                    "description": "The key to read (optional, use * for wildcards, e.g. 'app1/*')",
                },
                "label": {
                    "type": "string",
                    "description": "The label filter (optional, use '\\0' for no label, '*' for any label)",
                },
            },
            "required": [],
        },
  • Helper method in AzureResourceManager to obtain the AzureAppConfigurationClient instance used by the tool handler.
    def get_app_configuration_client(
        self, endpoint: str | None = None
    ) -> AzureAppConfigurationClient:
        """Get an Azure App Configuration client using AzureCliCredential."""
        try:
            logger.info(f"Creating AzureAppConfigurationClient")
            endpoint = endpoint or os.getenv("AZURE_APP_CONFIGURATION_ENDPOINT")
            if not endpoint:
                raise ValueError(
                    "Azure App Configuration endpoint is not specified and not set in the environment."
                )
    
            return AzureAppConfigurationClient(base_url=endpoint, credential=self.credential)
        except Exception as e:
            logger.error(f"Failed to create AzureAppConfigurationClient: {e}")
            raise RuntimeError(f"Failed to create AzureAppConfigurationClient: {e}")
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('Read') without detailing aspects like authentication requirements, rate limits, error handling, or what happens if parameters are omitted (e.g., default behavior). This leaves significant gaps for a tool that interacts with a cloud service.

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 any unnecessary words. It is front-loaded and appropriately sized for its simple function.

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 complexity of interacting with Azure App Configuration, no annotations, and no output schema, the description is insufficient. It lacks details on return values, error cases, or behavioral nuances, making it incomplete for effective agent use in a real-world scenario.

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 description coverage is 100%, so the input schema fully documents both parameters ('key' and 'label') with descriptions and optionality. The description adds no additional semantic context beyond what's in the schema, resulting in the baseline score of 3.

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 verb ('Read') and resource ('key-values from Azure App Configuration'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'app_configuration_kv_write' or 'app_configuration_kv_delete' beyond the verb choice, which is why it doesn't reach a perfect score.

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 sibling tools like 'app_configuration_kv_write' for writing or 'app_configuration_kv_delete' for deletion, nor does it specify any prerequisites or contextual cues for selection.

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