cloudflare-mcp-pro

kv_get

Read-only

Retrieve the value of a key in a Cloudflare KV namespace. Specify account ID, namespace ID, and key.

Instructions

Read the value of a key in a KV namespace.

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": {
      "namespace_id": "<namespace_id>",
      "key": "<key>"
    },
    "name": "kv_get"
  }
}

Input Schema

Name	Required	Description
`account_id`	No	Cloudflare account ID. Falls back to CLOUDFLARE_ACCOUNT_ID env var when omitted.
`namespace_id`	Yes	KV namespace ID.
`key`	Yes	The key to read.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 22, 2026

TDQS

A3.6/5.0

Behavior2/5

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

The description only says 'read the value' and adds no behavioral details beyond what annotations already provide (readOnlyHint, openWorldHint). It does not mention handling of missing keys, return type, or potential errors, which are important for a get operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, no fluff, and appropriately sized for a simple operation. However, it could include slightly more detail without becoming verbose.

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?

Given the tool's simplicity and the schema covering all parameters, the description is mostly adequate. However, it lacks information on return behavior (e.g., what is returned if key does not exist) and no output schema is provided, leaving some gaps.

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?

The schema has 100% description coverage; the description adds value by noting that account_id falls back to an environment variable when omitted, providing useful context beyond the schema.

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 'Read the value of a key in a KV namespace', specifying the verb (read) and resource (key in KV namespace). This distinguishes it from sibling tools like kv_put and kv_delete.

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?

No explicit guidance on when to use this tool versus alternatives. While the purpose is clear, the description does not mention when not to use it or provide context for selection among similar KV operations.

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

Deploy Server