Skip to main content
Glama
Sign In
plunger

plunger

Official
by metamug
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

list_saved_requests

Read-only

Lists the requests a user saved in Plunger, including name, method, URL, headers, and required {{variables}}, so agents can reuse existing calls before building new ones.

Instructions

List the requests the user saved in Plunger, by name, with method, URL, headers and the {{variables}} each needs. Call this before building a request from scratch: the user may already have the exact call set up.

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": "list_saved_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoOnly the ones in this group, or under it ("Jira" includes "Jira/Issues").

Output Schema

NameRequiredDescriptionDefault
requestsYesThe saved requests, by name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • changedOutput schema / $defs / StoredRequestInfo / properties / body_type / description
      Previous value: -"none, json, form-data, x-www-form-urlencoded or raw."New value: +"none, json, xml, form-data, x-www-form-urlencoded or raw."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read; the description adds that results carry method/URL/headers and resolved {{variables}}, which is useful context about the shape of the data. It says nothing about ordering, result volume, or whether listing has side effects on the saved set — with an output schema present, the return-field summary is partly redundant.

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, no filler, with the what (list saved requests plus their fields) front-loaded and the when (before building a request) trailing. Every clause carries information.

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 a single optional parameter fully documented, readOnlyHint set, and an output schema covering returns, the description does everything needed to call the tool. Only minor gaps remain, such as whether the list is paginated or unbounded.

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 group parameter's own description already explains the hierarchy semantics ("Jira" includes "Jira/Issues"). The tool description says nothing further about group, so the schema does all the work — 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 (list saved requests in Plunger) and enumerates the returned fields (name, method, URL, headers, variables), which makes it distinguishable from the singular get_saved_request sibling. It stops short of explicitly naming that sibling, so the differentiation relies on the list-vs-get reading.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call this before building a request from scratch: the user may already have the exact call set up" gives a clear triggering condition and a rationale, which is real routing guidance. It does not name concrete alternatives (get_saved_request, import_curl, send_request) or state when not to call it.

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

Deploy Server

Other Tools