Skip to main content
Glama
Sign In
Gud API MCP Server

Gud API MCP Server

Official
by gudlab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_collection

Retrieve all details of an API collection: folders, requests with method/URL/headers/body, and variables. Useful for exporting or inspecting collection contents.

Instructions

Get the full contents of one collection: folders, requests (with method/url/headers/body), and variables. Example response bodies are summarized.

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>"
    },
    "name": "get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
collectionYesCollection id or name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It describes what is returned but does not disclose any behavioral traits such as safety, permissions, or side effects.

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-load the key action without wasted words. Every sentence adds value.

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?

For a tool returning complex nested data, the description lacks details on response structure, format, or any limitations. Mentioning that example response bodies are summarized is vague and insufficient without output schema.

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%, so baseline is 3. The description does not add meaning beyond the schema's parameter description of 'Collection id or name.'

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 it retrieves full collection contents including folders, requests with details, and variables. It distinguishes from siblings like list_collections (presumably listing only names) and get_active_environment.

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?

The description implies use when full collection data is needed, but lacks explicit guidance on when to prefer this over alternatives or when not to use 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