agent-procurement-manager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APM_BASE_URL | No | Override the APM endpoint used by the local stdio bridge. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apm_quoteA | Get a free price quote from Agent Procurement Manager for a data task (categories: token_risk, wallet_onchain, web_search, data_enrichment, market_data, crypto_market, social_data, due_diligence). No charge, no execution. |
| apm_previewA | Free taster: compare the top-3 suppliers APM would buy from for a task, with the customer price. No execution, no payment. |
| apm_categoriesB | List the categories and verified suppliers currently available through Agent Procurement Manager. |
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 3 tools
apm_quote and apm_preview both return free pricing information with no execution or payment, making their boundary somewhat fuzzy—one is a single price, the other a top-3 supplier comparison. Descriptions do clarify the distinction, but an agent must read carefully to pick correctly. apm_categories is clearly distinct.
All three tools share the apm_ prefix followed by a single descriptive noun/verb (quote, preview, categories), giving a predictable and readable pattern. Minor deviation in that 'quote' and 'preview' are verbs/nouns of different types, but overall consistent.
Three tools is thin for a procurement domain and feels borderline—especially since the surface stops at quoting and never reaches actual purchasing. The low count is coherent with a quote-only gateway, but leaves it feeling underbuilt.
The tool set is a dead end: it can quote prices, compare suppliers, and list categories, but there is no way to actually place an order or execute a purchase, nor check order status. For an 'agent procurement manager' the core transaction lifecycle is entirely missing.