agentgauge
Server Details
Scan any website's AI readiness: AI search visibility and AI agent usability. Free, no auth.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- GlassCaseOfEmotion/agentgauge-skill
- 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 3.4/5 across 1 of 1 tools scored.
With only one tool, there is no risk of confusion or overlap between tools.
The single tool name follows a clear verb_noun pattern (scan_website), which is consistent within the set.
A single tool for an agent-readiness scanner is acceptable but minimal. It covers the core scanning action, but lacks auxiliary tools for configuration or results management.
The tool appears to provide a complete scan workflow, returning all relevant data. Minor gaps could include lack of tools for scheduling or comparing scans, but the main purpose is served.
Available Tools
1 toolscan_websiteScan a website for AI readinessBInspect
Run an AgentGauge agent-readiness scan of a website. Grades whether AI search can find/cite it and whether AI agents can use/transact with it, against the AgentReady standard. Returns the grade, both gauges, every check with its status, and a link to the full report.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The website URL or domain to scan, e.g. "example.com" |
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 mentions 'scan' (likely read-only) but does not explicitly state whether it is a read operation, if authentication is needed, if it is a long-running process, or any side effects. The description gives minimal behavioral context.
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 at two sentences, but the first sentence could be slightly more front-loaded on the essential action and return values. It avoids unnecessary words, but the structure is adequate.
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 single parameter and no output schema, the description covers what the tool returns and its purpose. However, it lacks explanation of the 'AgentReady standard' and the meaning of 'gauges', which may leave some ambiguity for the agent.
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 100% coverage for the single parameter 'url', with a clear description in the schema. The description adds no additional meaning beyond what the schema already provides, so a baseline score of 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 uses specific verbs ('Run an AgentGauge agent-readiness scan') and identifies the resource ('a website'). It explains what it grades (AI search findability and agent transactability) and what it returns (grade, gauges, checks, link). No sibling tools exist, so 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for scanning websites for AI readiness, but it does not provide explicit guidance on when to use vs. alternatives (since no siblings are listed). It lacks when-not-to-use instructions or context-appropriate scenarios.
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!