Agent Commerce Guard
Server Details
Policy review and purchase discovery for AI-agent commerce actions.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- fxjim/agent-commerce-guard
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 1 of 1 tools scored.
Only one tool exists, so there is no risk of confusion between tools. The tool's description clearly defines its purpose.
With a single tool, naming is inherently consistent. The verb-noun pattern 'review_actions' is clear and follows common conventions.
One tool is on the low side for a server named 'Agent Commerce Guard'. While the tool covers a specific review function, a broader scope would typically require more tools.
The server only provides a review function, explicitly excluding execution, payment, and other common commerce actions. For a guard service, this is a significant gap; agents have no way to act on the reviewed actions.
Available Tools
1 toolreview_agent_commerce_actionsReview agent commerce actionsARead-onlyIdempotentInspect
Review up to five non-sensitive public AI-agent actions for approval and evidence requirements. This tool does not execute, pay, sign, deploy, post, or reveal purchase instructions.
| Name | Required | Description | Default |
|---|---|---|---|
| actions | Yes | Actions to review. Do not submit secrets, private source, or customer data. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the tool as read-only and non-destructive. The description adds behavioral context by stating it does not execute, pay, sign, deploy, post, or reveal purchase instructions, which goes beyond annotations. However, it does not describe the review outcome or side effects beyond what annotations imply.
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?
Two sentences with no fluff: first states the action, second states exclusions. Every sentence is necessary and front-loaded.
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?
While the purpose is clear, the description omits details about what the review produces (output) and the 'evidence requirements' concept. Without an output schema, the agent lacks information on expected results.
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% and includes warnings about not submitting secrets. The description reinforces the non-sensitive constraint and the max of five actions, adding marginal value. Baseline 3 is appropriate.
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 clearly states the tool reviews up to five non-sensitive public AI-agent actions for approval and evidence requirements, and explicitly lists what it does not do (execute, pay, sign, deploy, post, reveal purchase instructions). This provides specific verb+resource+scope and distinguishes from potential siblings.
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?
The description indicates when to use (for review and approval of actions) and what not to submit (non-sensitive only). Although there are no sibling tools to differentiate from, the context is clear and includes constraints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!