Skip to main content
Glama
Sign In
Gud API MCP Server

Gud API MCP Server

Official
by gudlab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_request

Remove a saved API request from a collection using its id or name. Clean up your Gud API collections efficiently.

Instructions

Delete a saved request from a collection by id or name.

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

Input Schema

NameRequiredDescriptionDefault
requestYesRequest id or name.
collectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, and the description does not disclose the permanence of deletion, side effects (e.g., impact on other collections or requests), required permissions, or error handling. For a destructive operation, more transparency is needed.

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?

The description is a single sentence with no superfluous words. Every part is functional and front-loaded.

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 annotations, no output schema, and only partial parameter documentation, the description is insufficient for an agent to understand the full behavior (e.g., return value, id format, case sensitivity). It relies on assumptions.

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?

The description adds minimal value beyond the schema: it confirms 'request' can be an id or name, and 'collection' is the container. However, the schema already describes 'request' (50% coverage), and the collection parameter lacks description both in schema and text. The description does not compensate fully for the missing schema description.

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?

The description clearly states the verb 'Delete', the resource 'saved request', the context 'from a collection', and the method 'by id or name'. This distinguishes it from sibling tools like 'create_collection' or 'send_request'.

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 guidance is provided on when to use this tool versus alternatives (e.g., when to delete by id vs name, or when not to delete). The description is purely declarative.

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