Postman MCP Generator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| post_dataC | Post data to the Ucode Items API. |
| get_dataC | Get data from the Ucode Items API. |
| delete_dataC | Delete data from the Ucode Items API. |
| update_dataC | Update data on the Ucode Items API. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: delete, get, post, and update data, with no overlap in functionality. The action verbs (delete, get, post, update) are unambiguous and map directly to standard HTTP methods, making it easy for an agent to select the correct tool.
All tool names follow a consistent verb_noun pattern (e.g., delete_data, get_data, post_data, update_data), using snake_case uniformly. This predictable naming scheme enhances readability and usability for agents.
With 4 tools, the set is well-scoped for the Ucode Items API domain, covering the essential CRUD operations (create, read, update, delete). This count is appropriate, as each tool earns its place without being excessive or insufficient for the server's purpose.
The tool set provides complete CRUD coverage for the Ucode Items API, with no obvious gaps. It includes post_data (create), get_data (read), update_data (update), and delete_data (delete), ensuring agents can handle the full lifecycle of data operations without dead ends.