Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Get Resource Reference Tool

get-resource-reference
Read-onlyIdempotent

Returns an MCP client-usable resource reference for a specified text or blob resource ID, enabling clients to fetch the intended resource.

Instructions

Returns a resource reference that can be used by MCP clients

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-reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceIdNoID of the text or blob resource to fetch, a positive integer
resourceTypeNoWhether to reference a text resource or a blob resourceText

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds only the vague claim that the result is consumable by MCP clients; it says nothing about whether fetching resolves or merely constructs the reference, or whether side effects occur (contrast sibling trigger-resource-update).

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?

It is a single short sentence with no filler, which is structurally clean, but the brevity is under-specification rather than earned concision given an undefined return concept. Front-loading is fine; there is simply very little to front-load.

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?

With no output schema, the description is the only place an agent could learn the shape and meaning of the returned reference, and it does not provide it. For a two-optional-param tool with full schema coverage the input side is fine, but the return side — the tool's entire purpose — is left opaque.

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%, with resourceId documented as a positive integer and resourceType as an enum, so the schema carries parameter meaning. The description adds nothing about how the two parameters interact (e.g., that resourceType selects which resource namespace the ID is resolved in), which is the only param-level value it could add here.

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 a verb and resource ('Returns a resource reference'), which is more than a restatement of the name, but 'resource reference' is never defined (URI, handle, ID?) and it draws no distinction from siblings such as get-resource-links or get-resource-links/get-structured-content.

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?

No when-to-use guidance at all: no condition for choosing this over get-resource-links or the other get-* siblings, no prerequisites, no statement of what the caller should do with the result. The phrase 'can be used by MCP clients' implies a usage but does not specify one.

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