Skip to main content
Glama
Sign In
cloudflare-mcp-pro

cloudflare-mcp-pro

by helbertparanhos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_tunnel

Read-only

Retrieve detailed information about a specific Cloudflare Tunnel using its ID.

Instructions

Get details of a Cloudflare Tunnel 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": {
      "tunnel_id": "<tunnel_id>"
    },
    "name": "get_tunnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoCloudflare account ID. Falls back to CLOUDFLARE_ACCOUNT_ID env var when omitted.
tunnel_idYesTunnel ID (from list_tunnels).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's 'Get details' is consistent. No additional behavioral traits (e.g., authorization, rate limits) are disclosed.

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, front-loaded sentence of 9 words with zero redundancy, efficiently conveying the tool's core purpose.

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

Completeness4/5

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

For a simple read operation with two well-described parameters and no output schema, the description adequately covers purpose. It could mention that it returns full tunnel configuration, but current version is sufficient.

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 covers 100% of parameters with clear explanations (account_id fallback, tunnel_id source). The description adds no extra meaning beyond what the schema provides.

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 uses the specific verb 'Get' and clearly identifies the resource as 'details of a Cloudflare Tunnel by ID,' which distinguishes it from sibling tools like list_tunnels.

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 a tunnel ID is available but does not explicitly state when to use this tool over siblings (e.g., list_tunnels to find IDs) or provide exclusion criteria.

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

Deploy Server

Other Tools