vercel-mcp-pro

get_edge_config

Gets metadata for a single Edge Config store by its ID. Accepts optional team scoping parameters.

Instructions

Get metadata for a single Edge Config store by id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "edgeConfigId": "<edgeConfigId>"
    },
    "name": "get_edge_config"
  }
}

Input Schema

Name	Required	Description
`edgeConfigId`	Yes	Edge Config id (ecfg_...).
`teamId`	No	Team ID to scope the request. Falls back to VERCEL_TEAM_ID when omitted.
`slug`	No	Team slug to scope the request (alternative to teamId).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 11, 2026

TDQS

A3.5/5.0

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 (get metadata) but does not explain error handling, authentication requirements, rate limits, or what happens if the ID is invalid. The description is too sparse to be transparent.

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 sentence of 12 words, perfectly front-loaded with the verb and subject. Every word is necessary, and there is no redundancy or filler.

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

Completeness3/5

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

For a simple get-by-ID operation with a well-defined schema, the description covers the core functionality. However, it does not explain what 'metadata' encompasses, nor does it address potential errors or output structure (no output schema). Slightly more detail would improve completeness.

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 already describes all three parameters with 100% coverage. The description adds no additional meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 retrieves metadata for a single Edge Config store by ID. It distinguishes itself from sibling tools like 'list_edge_configs' (lists all) and 'get_edge_config_items' (retrieves items), making the purpose unambiguous.

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?

The description implies usage when you have a specific Edge Config ID, but it does not explicitly state when to use this tool versus alternatives like 'list_edge_configs' to first obtain IDs, or 'get_edge_config_items' for items. No exclusion criteria or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server