Skip to main content
Glama

Show request

get_request
Read-onlyIdempotent

Retrieve one saved request’s full definition—URL, headers, body, auth, variables, assertions, extraction rules, scripts, saved example names, and revision—so you can inspect or update it safely.

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. revision identifies this version for save_request.

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": {
      "request": "<request>"
    },
    "name": "get_request"
  }
}

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
revisionNo
mcpMethodNo
preScriptNo
assertionsNo
extractorsNo
grpcMethodNo
postScriptNo
grpcMessageNo
graphqlQueryNo
mcpArgumentsNo
graphqlVariablesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.1
    • addedOutput schema / properties / revision
      Added value: +{
      +  "type": "string"
      +}
  2. 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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior beyond that: credentials are masked, variables render as {{name}}, options shows only non-default settings, and revision is the token save_request expects. Return shape is largely left to the output schema, which exists.

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?

Front-loaded with the core action, then a compact enumeration, then the three non-obvious behaviors (masking, variable rendering, options diffing). Every sentence carries distinct information with no filler or repetition.

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

Completeness5/5

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

For a one-parameter read tool with full annotation coverage and an output schema, this is complete: it tells the agent what comes back, how sensitive fields and variables are rendered, and how the returned revision feeds into save_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?

Schema coverage is 100% and the schema itself already explains that request accepts an id or name and that duplicate names need a folder path. The description adds no further meaning about the single parameter, so the baseline 3 applies.

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?

States a specific verb and resource ("Show one saved request in full") and enumerates exactly what is returned: URL, headers, body, auth, vars, assertions, extraction rules, scripts, example names. The singular "one saved request" implicitly separates it from list_requests, though no sibling is named explicitly.

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: an agent infers this is the inspection tool for a single saved request, and "revision identifies this version for save_request" hints at the read-then-write workflow. There is no explicit when-to-use statement, no exclusion of alternatives like last_response or send_request, and no stated prerequisites.

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