Skip to main content
Glama
Sign In
postman-mcp-server

postman-mcp-server

by delano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_environments

Lists all environments in a workspace. Defaults to 'My Workspace' if no workspace ID provided.

Instructions

List all environments in a workspace. If workspace not specified, lists environments in "My Workspace".

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_environments"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoWorkspace ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description must carry full burden. Only discloses listing behavior; lacks details on pagination, sorting, permissions, or response structure. Minimal disclosure for a list operation.

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, each serving a distinct purpose: main action and default behavior. No superfluous words, front-loaded. Ideal conciseness.

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

Completeness3/5

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

Simple tool with one optional parameter. No output schema so return format is implied but not stated. Adequate but could mention that it returns an array of environment objects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers parameter description (Workspace ID optional) at 100%. Description adds value by explaining default behavior when workspace is omitted ('My Workspace'), which is not in schema.

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?

Description states 'List all environments in a workspace' with clear verb and resource. It distinguishes from siblings like get_environment (single) and create_environment (creation). Lacks explicit mention of list format but purpose is clear.

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 on when to use this tool vs alternatives like get_environment for a single environment. Only mentions default workspace behavior but no when-not-to-use or comparative context.

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