Skip to main content
Glama

Get one of my requests

request_get
Read-onlyIdempotent

Details of one of your own requests by reference: status, what you submitted (wrapped as data) and attached file metadata. Someone else's reference returns not found.

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": {
      "ref": "<ref>"
    },
    "name": "request_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesRequest reference from requests_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower; the description still adds real behavior of its own by disclosing that submitted content is wrapped as data, that file metadata (not file contents) is returned, and that a foreign reference yields not-found rather than an authorization error. It does not describe pagination or how large payloads are truncated, which is a minor omission for a single-record read.

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

Conciseness5/5

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

Two sentences, front-loaded with the verb and resource, followed immediately by the returned fields and then the ownership caveat. No filler, no repetition of the title, nothing an agent must read twice.

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

Completeness4/5

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

With one required parameter, full schema coverage, and a rich annotation set, the description supplies everything an agent needs to call it correctly and to anticipate the response shape even though no output schema exists. Only edge behavior — error variants beyond not-found, or handling of very large submission payloads — is left unstated.

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?

Schema coverage is 100% and the schema already documents the single ref parameter, its accepted formats, and its origin in requests_list. The description adds meaning beyond that by tying the argument to an ownership constraint — only your own references resolve, others return not found — which changes how an agent should source and validate the value.

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

Purpose5/5

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

States a specific verb (get details of) and a precisely scoped resource (one of your own requests by reference), then enumerates what comes back: status, submitted payload, and attached file metadata. The ownership scoping ('your own') distinguishes it from catalog-style or list-style siblings without ambiguity.

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?

Usage is implied rather than stated: 'by reference' plus the schema note pointing at requests_list tells the agent this is a follow-up lookup to a list result. The 'someone else's reference returns not found' line usefully rules out cross-owner lookups, but no alternative tool is ever named for fetching other people's requests or for listing requests to obtain a reference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources