Periskop MCP Serverofficial
A
license-
qualityC
maintenanceEnables AI agents to perform product discovery from natural language shopping intents, returning ranked products with merchant links without completing checkout.
MIT
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
- Server Listing
- agent-commerce-guard
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A4/5.0
Tool DescriptionsA
Average 4.4/5 across 1 of 1 tools scored.
Server CoherenceB
Disambiguation5/5
With only one tool, there is no possibility of confusion with other tools. The tool's purpose is clearly distinct.
Naming Consistency5/5
The single tool name follows a clear verb_noun pattern (review_agent_commerce_actions), so there is no inconsistency.
Tool Count1/5
A single tool is far too few for a server claiming to be a 'commerce guard'. The tool only reviews actions and does not handle execution, approval flow, or sensitive actions, making the scope extremely narrow.
Completeness1/5
The tool is severely limited: it only reviews non-sensitive public actions up to five. There are obvious gaps such as handling sensitive actions, executing approved actions, or managing more than five actions, leaving the domain largely uncovered.
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| actions | Yes | Actions to review. Do not submit secrets, private source, or customer data. |
Tool Definition Quality
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true and idempotentHint=true. The description adds behavioral context by explicitly listing actions the tool does not perform (execute, pay, sign, deploy, post, reveal), which reinforces safety and provides clarity beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, each serving a distinct purpose: first defines the core function, second lists key exclusions. No wasted words, front-loaded with essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given low complexity (1 param, no output schema, no siblings), the description adequately covers purpose, input constraints, and exclusions. However, it does not explain what 'evidence requirements' entails or the form of the review output, leaving minor gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers 100% of parameters with descriptions, but the tool description adds important context: limiting to non-sensitive public actions and a maximum of five. This expands on the schema's generic 'actions' parameter, adding meaning about content and scale.
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 clearly states the verb 'Review' and the resource 'non-sensitive public AI-agent actions' with a specific scope (up to five). It explicitly lists actions the tool does NOT perform, distinguishing its role. With no sibling tools, differentiation is not needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implicitly guides usage by stating exclusions (does not execute, pay, etc.), indicating this is a pre-execution review tool. However, it lacks explicit when-to-use or when-not-to-use guidance, but the clarity of exclusions compensates partially.
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!
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to create, compare, and track purchases with structured buying workflows, offer comparison, and merchant verification.5MIT
- AlicenseBqualityBmaintenanceMachine-readable merchant verification infrastructure for AI shopping agents and agentic commerce systems.13MIT
Nexbidofficial
Alicense-qualityBmaintenanceAgentic commerce infrastructure for AI agents. MCP-native product discovery, contextual ad matching, and purchase facilitation with European privacy compliance (nDSG/GDPR).MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.