Skip to main content
Glama
Sign In

Agent Procurement Manager (APM)

by io.github.lgs1520
OverviewDiscussionsAdmin

apm_preview

Free supplier-selection preview ("free sample"): returns the top-3 candidate suppliers APM would consider — names, unit prices, score breakdown, expected latency, historical success rate — plus the supplier that would be selected and the customer price. Executes nothing and charges nothing. This tool is free and never executes a purchase. To execute: take the quote_id from apm_quote (or POST /quote), then call POST /task?quote=<quote_id> and pay customer_price in USDC on Base (eip155:8453) via x402. Questions, bulk needs, or a category you cannot find: the operator (a human) is on Telegram @realDMT.

Input Schema

NameRequiredDescriptionDefault
taskYesWhat you need done
inputNoToken/wallet address, or search query text
categoryNo
caller_idNoOptional: your APM caller_id from apm_register — present it and APM recognizes you and remembers this ask (category + price only)
max_budgetNoMax you will pay in USDC

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "token_risk",
-  "wallet_onchain",
-  "web_search",
-  "due_diligence",
-  "data_enrichment",
-  "market_data",
-  "crypto_market",
-  "social_data"
-]New value: +[
+  "token_risk",
+  "wallet_onchain",
+  "web_search",
+  "due_diligence",
+  "data_enrichment",
+  "market_data",
+  "crypto_market",
+  "social_data",
+  "prediction_market"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / caller_id
      Added value: +{
+  "description": "Optional: your APM caller_id from apm_register — present it and APM recognizes you and remembers this ask (category + price only)",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "token_risk",
-  "wallet_onchain",
-  "web_search",
-  "due_diligence",
-  "data_enrichment"
-]New value: +[
+  "token_risk",
+  "wallet_onchain",
+  "web_search",
+  "due_diligence",
+  "data_enrichment",
+  "market_data",
+  "crypto_market",
+  "social_data"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "token_risk",
-  "wallet_onchain",
-  "web_search"
-]New value: +[
+  "token_risk",
+  "wallet_onchain",
+  "web_search",
+  "due_diligence",
+  "data_enrichment"
+]
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it states 'Executes nothing and charges nothing' twice, describes exactly what data is returned, and clarifies that actual payment occurs only later on Base via x402. This gives an agent a clear safety and capability profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the preview's purpose and return values, then covers execution and operator contact. It is slightly long, but most sentences provide routing or safety information that earns its place.

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

Completeness5/5

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

There is no output schema, but the description enumerates the return fields (supplier names, unit prices, score breakdown, latency, success rate, selected supplier, customer price). It also explains the free preview versus paid execution flow, making the definition complete for this tool.

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 description coverage is 80%, so the schema already documents most parameters. The description adds useful context about quote_id and execution, but quote_id is not an input parameter here, and it does not add meaning beyond the schema for task, input, category, caller_id, or max_budget.

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 states a precise verb and resource: a free supplier-selection preview that returns top-3 candidate suppliers and pricing details. It clearly distinguishes the tool from apm_quote by explaining that apm_quote provides the quote_id needed for execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly describes when to use this tool versus the execution path: preview for free/non-executing selection, then apm_quote/post quote for a quote_id, then POST /task for purchase. It also routes edge cases such as questions or bulk needs to a human operator.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Procurement Manager (APM) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources