Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Get Structured Content Tool

get-structured-content
Read-onlyIdempotent

Retrieve structured content for a selected city and return an output schema so clients can validate the data.

Instructions

Returns structured content along with an output schema for client data validation

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": {
      "location": "<location>"
    },
    "name": "get-structured-content"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYesChoose city

Output Schema

NameRequiredDescriptionDefault
humidityYesHumidity percentage
conditionsYesWeather conditions description
temperatureYesTemperature in celsius

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds some context by mentioning an output schema for client-side validation, but it does not describe permissions, side effects, or data scope beyond that.

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 front-loaded sentence with no filler or redundant wording. It is efficient, though its brevity leaves important selection context unstated.

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?

This is a simple one-parameter tool, and the presence of a rich input schema, output schema, and detailed annotations reduces what the description must carry. Still, it omits the location-based nature of the result and any usage context, leaving it only minimally complete.

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%, and the single location parameter is fully documented with an enum in the schema. The description adds no additional parameter meaning, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool returns structured content plus an output schema, which gives a general verb and resource. However, 'structured content' is vague and it does not indicate that the returned content is city-based or distinguish this tool from sibling getters.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description implies it is a getter but provides no prerequisites, exclusions, or sibling routing advice.

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