botguard-pro
Server Details
Bot traffic detector for paid ads. Input: domain. Returns trigger, fake sessions, daily USD waste.
- 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 3.6/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion with other tools.
With a single tool, naming is trivially consistent.
A single tool for a service named 'botguard-pro' suggests a broader scope; one tool feels thin for a comprehensive ad traffic analysis service.
The tool only checks ad traffic, but lacks related operations like managing whitelists, viewing history, or configuring alerts, leaving significant gaps for the expected domain.
Available Tools
1 toolcheck_ad_trafficAInspect
Detects bot traffic and wasted ad spend for a site. Input: site_id (string). Returns: trigger (bool), paid_sessions (int), estimated_wasted_per_day (float in USD). Use when diagnosing ROAS drops or invalid clicks on paid campaigns.
| Name | Required | Description | Default |
|---|---|---|---|
| site_id | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavioral traits. It only lists return fields without explaining side effects, authentication requirements, rate limits, or whether the operation is read-only. The absence of such context leaves the agent uninformed about important behavioral aspects.
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 extremely concise: two well-structured sentences. The first sentence states the core purpose and output, the second provides input and usage context. Every word serves a purpose, with no redundancy or unnecessary details.
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?
Given the tool's simplicity (1 parameter, no output schema), the description covers the essential aspects: purpose, input, output types, and use case. However, it does not elaborate on the meaning of the return fields (e.g., what 'trigger' indicates, thresholds for wasted spend), leaving some ambiguity. It is adequate but not fully comprehensive.
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?
The schema has 1 parameter (site_id) with 0% description coverage. The description merely restates 'Input: site_id (string)' without adding meaning like expected format, source, or constraints. The description adds minimal value beyond the schema, failing to compensate for the lack of schema descriptions.
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 detects bot traffic and wasted ad spend, with a specific verb 'detects' and resource 'ad traffic for a site'. It explicitly lists input and output fields, and distinguishes usage for diagnosing ROAS drops or invalid clicks, making the purpose unmistakable.
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 provides clear guidance on when to use the tool: 'Use when diagnosing ROAS drops or invalid clicks on paid campaigns.' It lacks explicit exclusion of other scenarios but the use case is well-defined. Since there are no sibling tools, no alternatives are needed, but the guidance is effective.
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!