Retrieve workspace details from Postman to manage API collections and environments. Provide the workspace ID to access configuration and collaboration settings.
Get details of a specific workspace
| Name | Required | Description | Default |
|---|---|---|---|
| workspace | Yes | Workspace ID | |
| include | No | Additional data to include in response |
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description must carry full burden. It only states a read operation ('Get details') without disclosing authorization needs, rate limits, or side effects. Minimal behavioral transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Very concise single sentence that is front-loaded. It earns its place but could be slightly more structured or informative without sacrificing brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, and the description does not explain what details are returned. While functional for a simple getter, it lacks completeness for an agent to fully understand the tool's output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already adequately documents parameters. The description adds no additional meaning beyond what is in the schema, leading to a baseline score.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Get details of a specific workspace' clearly states the action and resource. However, it does not differentiate from sibling tools like get_workspace_roles or get_workspace_tags, which also fetch workspace details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives like list_workspaces. The usage is implicitly clear for fetching a single workspace, but lacks when-to-use or when-not-to-use context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.