Perceptdot
Server Details
B2A2H platform — tracks GA4, Vercel deployments, GitHub workflows with AI-powered ROI analytics.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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.2/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion with other tools. The single tool's purpose is clearly distinct.
Consistency is trivial with a single tool. The name 'visual_check' follows a clear verb_noun pattern.
The server has only one tool, which is on the thin side for a typical server. While the tool itself is non-trivial, the limited count borders on being insufficient for broader use cases.
The tool covers a single action (visual check) but lacks other expected features such as comparing with baselines, listing past checks, or configuring thresholds. This represents a significant gap for a visual testing service.
Available Tools
1 toolvisual_checkAInspect
Screenshot a URL and analyze it for visual bugs using AI. Returns whether issues exist, a summary, and a detailed issues list. Use this after deployments, PRs, or any UI change to catch layout problems.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL to visually check (must be publicly accessible) | |
| prompt | No | Optional: specific aspect to focus on | |
| no_cache | No | Optional: bypass cache | |
| viewport | No | Optional: viewport size — desktop (1280px), tablet (768px), mobile (375px) |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It mentions screenshotting and analyzing but does not disclose potential side effects like caching behavior (despite a 'no_cache' parameter), rate limits, or authentication needs. The behavioral transparency is adequate but could be more explicit.
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?
The description is concise, with two sentences covering the main action and output, plus a one-sentence usage guideline. It is front-loaded with the core purpose and wastes no words.
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?
The tool has 4 parameters and no output schema. The description explains what it returns (issues, summary, list) but does not detail the structure or format of the return values. Given the lack of output schema, the description should provide more specifics for an AI agent to parse output correctly. Thus, completeness is moderate.
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 coverage is 100% with descriptions, and the tool description adds value by clarifying that the URL must be publicly accessible and providing pixel values for viewport sizes. This goes beyond what the schema alone provides.
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's action ('Screenshot a URL and analyze it for visual bugs using AI') and its output ('Returns whether issues exist, a summary, and a detailed issues list'). It is specific about the resource (URL) and purpose (catch layout problems).
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 explicitly recommends using the tool after deployments, PRs, or UI changes to catch layout problems. While it does not mention when not to use it or alternatives, the context is clear and actionable.
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!