Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Get Resource Links Tool

get-resource-links
Read-onlyIdempotent

Return up to ten resource links pointing to different resource types, with a configurable count from 1 to 10, to support resource discovery and selection.

Instructions

Returns up to ten resource links that reference different types of resources

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-resource-links"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of resource links to return (1-10)

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is fully covered. The description adds only the ten-item cap, which is also implied by the schema maximum, and says nothing about what a "resource link" contains or how results are ordered.

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?

One short, front-loaded sentence with no filler or repetition. Its brevity is appropriate, though the same brevity contributes to the vagueness noted elsewhere rather than by itself being a flaw.

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?

The tool is simple, annotations are rich, and the only parameter is fully documented. But with no output schema, the description should explain what a returned resource link looks like or how many/which types appear, and that is missing.

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 count parameter already documents its 1-10 range and default of 3. The description's "up to ten" merely restates the schema maximum, adding no new meaning about what count controls semantically.

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 names a verb ("Returns") and a resource ("resource links"), and states an upper bound of ten. However, "different types of resources" is vague and does nothing to distinguish it from the sibling get-resource-reference, so an agent cannot tell the two apart from the text alone.

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 call this instead of get-resource-reference or any other sibling, nor any stated precondition or exclusion. The agent must infer the intended usage entirely from the name and the count parameter.

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