Skip to main content
Glama

Show request

get_request
Read-onlyIdempotent

Retrieve one saved request in full—URL, headers, body, auth, variables, assertions, extraction rules, scripts, and example names—to inspect or edit it, with secrets masked.

Instructions

Show one saved request in full: URL, headers, body, auth settings, its own variables (vars), assertions, extraction rules, scripts and the names of its saved examples. Credentials are masked; variables appear as {{name}}. options lists only the settings that differ from the defaults.

Input Schema

NameRequiredDescriptionDefault
requestYesThe request's id, or its name. A name that is used twice needs its folder path in front, as list_requests shows it, such as auth/Login.

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
authNo
bodyNo
nameNo
varsNo
folderNo
methodNo
headersNo
mcpToolNo
optionsNo
bodyTypeNo
examplesNo
mcpMethodNo
preScriptNo
assertionsNo
extractorsNo
grpcMethodNo
postScriptNo
grpcMessageNo
graphqlQueryNo
mcpArgumentsNo
graphqlVariablesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.19

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent read, so the description doesn't need to cover safety. It adds genuinely useful behavioral detail the schema cannot: credentials are masked, variables are rendered as {{name}}, and options lists only non-default settings — all of which shape how the agent should interpret the output.

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?

Three compact sentences, front-loaded with the resource and the full field list, then the masking/variable rendering caveat. Dense but every clause carries information; minor cost is the long enumerated list read as a run-on.

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 an output schema present and rich annotations, the description needn't explain return shape or safety, and it covers the one thing schema can't — masking and variable substitution. The only real gap is routing guidance against list_requests/send_request for the same request.

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?

There is one parameter with 100% schema description coverage, and the schema already explains the id/name resolution and the folder-path disambiguation for duplicate names. The description adds no further parameter guidance, so the baseline of 3 applies.

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 (show) and resource (one saved request) and enumerates the contents returned (URL, headers, body, auth, vars, assertions, extractions, scripts, example names), which clearly distinguishes it from summary-level siblings like list_requests and from response-oriented tools like last_response.

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 only implied: 'one saved request' contrasts with list_requests in the parameter schema, and 'saved' implies a stored definition rather than a live response. There is no explicit statement of when to prefer this over list_requests or send_request, and no exclusions or prerequisites.

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