Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Get Tiny Image Tool

get-tiny-image
Read-onlyIdempotent

Returns a tiny MCP logo image for embedding as a compact visual asset or placeholder in MCP-related output.

Instructions

Returns a tiny MCP logo image.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-tiny-image"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and a closed-world scope, so the safety profile is fully covered. The description adds only the qualitative detail that the image is 'tiny'; it never says what form the result takes (image content block vs. base64 vs. URL) or its dimensions, which is the one behavioral fact an agent would still want with no output schema present.

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?

A single short sentence with zero filler and the essential information front-loaded. It is arguably too terse rather than too verbose, but nothing in it is wasted.

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?

For a trivial, parameterless read tool with no output schema and full annotation coverage, the description is nearly complete. The remaining gap is the return format and image characteristics, which the agent must discover by calling — acceptable for a demo tool but not fully closed.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The schema is empty and fully consistent with the description's claim that the call is unconditional.

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 states a concrete verb ('Returns') and a concrete resource ('a tiny MCP logo image'), so the agent knows exactly what comes back. It does not name or contrast any sibling, but no sibling in the list plausibly returns an image, so differentiation is largely unnecessary here.

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?

There is no explicit when-to-use, when-not-to-use, or alternative guidance. Usage is only implied by the narrowness of the purpose — an agent that needs an MCP logo image can infer it applies — which is the textbook 'implied usage' case rather than stated guidance.

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