Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Get Header Params Tool

get-header-params
Read-onlyIdempotent

Returns a region value and the Mcp-Param-Region HTTP header it arrived in to verify that x-mcp-header mirrors arguments into headers.

Instructions

Returns its region argument and the Mcp-Param-Region HTTP header it arrived in. Demonstrates x-mcp-header (a 2026-07-28 Streamable HTTP client mirrors the argument into the header) and JSON Schema 2020-12 input and output schemas.

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": {
      "region": "<region>"
    },
    "name": "get-header-params"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYesA region name, e.g. eu-west. Mirrored into the Mcp-Param-Region HTTP header.
repeatNoHow many times to repeat the region in the result (1-3)

Output Schema

NameRequiredDescriptionDefault
regionYes
repeatedYes
regionHeaderYesThe Mcp-Param-Region header the request carried, if any

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: the returned header only exists when a 2026-07-28 Streamable HTTP client mirrors the argument, which warns the agent the header may be absent or differ. It does not mention the repeat-count behavior, which is left to the schema.

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?

Two sentences, both substantive, with the return behavior front-loaded before the protocol rationale. Slight density of spec jargon ('x-mcp-header', '2026-07-28 Streamable HTTP') but no filler.

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?

An output schema exists so return values need no prose, and annotations carry the safety profile. The description covers the one non-obvious behavior (conditional header presence) and the demonstration intent; only the repeat parameter is left unexplained in prose.

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?

With 100% schema description coverage, the schema already documents both parameters, including the region-to-header mirroring. The description restates the mirroring idea but adds no format, constraint, or repeat semantics beyond the schema, so this sits at the baseline.

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 names a specific verb and result set: it returns the 'region' argument plus the 'Mcp-Param-Region' HTTP header the request arrived in, and frames itself as a demonstration of x-mcp-header and 2020-12 schemas. That is enough to distinguish it from the echo/get-env siblings, though it never explicitly says how it differs from them.

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 framing as a demonstration implies a diagnostic/verification use case, but there is no explicit when-to-use, when-not-to-use, or named alternative among the echo/get-* siblings. An agent must infer that this is for probing header mirroring rather than general data retrieval.

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