Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Get Annotated Message Tool

get-annotated-message
Read-onlyIdempotent

Generates example messages with annotations to demonstrate how metadata can describe error, success, or debug content.

Instructions

Demonstrates how annotations can be used to provide metadata about content.

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": {
      "messageType": "<messageType>"
    },
    "name": "get-annotated-message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageTypeYesType of message to demonstrate different annotation patterns
includeImageNoWhether to include an example image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond that: it does not explain what the tool returns, how messageType affects output, or what including an image does. It does not contradict the annotations, but it contributes almost nothing.

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

Conciseness3/5

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

The description is a single short sentence with no wasted words, so it is concise. However, it is not front-loaded with actionable information and reads as a vague demo statement rather than a structured tool definition.

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

Completeness2/5

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

The tool is simple, with two parameters and full schema coverage, but the description still fails to explain what the tool actually returns or how to use it. For a demo tool whose purpose is to illustrate annotations, the description should at least state that it returns a message with annotation metadata. It leaves the agent to infer too much from the name and schema.

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%, so both parameters are already documented in the input schema. The description adds no additional meaning about messageType enum values or includeImage behavior. Baseline 3 is appropriate because the schema carries the parameter semantics.

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

Purpose2/5

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

The description says only that the tool 'demonstrates how annotations can be used to provide metadata about content.' It does not state that it returns an annotated message, what kind of message, or how it differs from sibling demo tools. The purpose is essentially a restatement of the tool name rather than a specific verb-and-resource description.

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 guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description gives no indication of the scenario in which an agent should select get-annotated-message over other demo or message-related tools.

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