ProofLayered
Server Details
Free passive growth-bottleneck scan for B2B SaaS websites: visibility, trust, conversion, scale.
- 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.3/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion with other tools. The tool's purpose is clearly described.
With a single tool, there is no inconsistency. The name 'growth_bottleneck_scan' follows a descriptive verb_noun pattern that is clear.
The server has only one tool, which is too few for the apparent scope of growth bottleneck analysis. A comprehensive service would include multiple related operations.
The tool provides only a passive scan, but no further tools for detailed diagnosis or fixes. The workflow dead-ends by directing users to an external site for paid services, leaving obvious gaps in the MCP tool surface.
Available Tools
1 toolgrowth_bottleneck_scanAInspect
Free passive scan of a public B2B SaaS website. Returns bottleneck scores (visibility, trust, conversion, scale), the primary public growth blocker, and top fix priorities. Passive only: no credentials, no production access. Full signed diagnosis with deploy-ready fix packs is a flat $490 at prooflayered.com/app.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public company URL, e.g. https://example.com |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It states the tool is passive and non-destructive, which is good. However, it does not disclose error handling or rate limits, leaving some behavioral aspects unclear.
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 two concise sentences that are front-loaded with the primary purpose. No unnecessary words; every sentence adds value.
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 simplicity of the tool (one parameter, no output schema), the description is sufficiently complete. It explains what the tool does, its limitations, and the outputs. It also mentions the paid option for more in-depth analysis.
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%, so the schema fully documents the 'url' parameter. The description adds context by specifying 'public B2B SaaS website' and provides an example format. This adds value beyond the schema.
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 performs a free passive scan of a public B2B SaaS website and lists specific outputs (bottleneck scores, primary blocker, fix priorities). The verb 'scan' and resource 'public B2B SaaS website' are specific, and the scope is well-defined.
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 specifies that the tool is passive-only and requires no credentials or production access, indicating safe usage. It also mentions a paid upgrade for a full diagnosis, providing context for when to use the free version versus the paid service. However, it does not explicitly state when not to use the tool.
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!