surf
Server Details
Point Gecko at an OpenAPI spec; get first-call-correct, auth-hidden agent tools.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- GeckoVision/gecko-surf
- GitHub Stars
- 4
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.4/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion or overlap. The tool's purpose is clearly distinct.
With a single tool, naming consistency is perfect. The name 'comprehend_api' follows a clear verb_noun pattern and is descriptive.
The server has a narrow, specific purpose—comprehending APIs into agent tools. One tool is slightly minimal but still reasonable given the focused scope.
The single tool covers the core workflow of submitting an API URL and receiving artifacts. Missing auxiliary features like listing or deleting comprehensions, but the stated purpose is achieved without dead ends.
Available Tools
1 toolcomprehend_apiAInspect
Submit an API's OpenAPI URL (or a human docs page URL with from_docs=true) and get it comprehended into first-call-correct agent tools — no integration code. Returns the API name, its usable tools, agent-native artifacts (llms.txt / gecko.json / tools.md), and self-host next steps. Comprehends and returns to YOU only: it does not host, publicly list, or register your API.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The API's OpenAPI spec URL (or a docs page URL if from_docs). | |
| from_docs | No | Recover the surface from a human docs page instead of an OpenAPI spec. Results are quarantined pending review. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that results are private, that from_docs results are quarantined, and that it does not host or register. This adds significant behavioral context beyond the schema.
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 only a few sentences that are front-loaded. Every sentence adds value, no wasted 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?
Given no output schema, the description adequately explains return values (API name, tools, artifacts, next steps). It also addresses the special case of from_docs. However, could mention rate limits or authentication briefly.
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%. The description adds context: indicates that 'url' can be an OpenAPI spec or human docs page (with from_docs=true), and notes that from_docs results are quarantined. This provides extra meaning 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 action (submit an API's URL), the resource (OpenAPI URL or human docs page), and the outcome (comprehend into agent tools), distinguishing it from any potential siblings. It specifies what the tool does and what it returns.
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?
Describes the primary use case and emphasizes privacy (returns to YOU only, does not host/list/register). While it doesn't mention explicit alternatives, the context is clear for when to use this 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!