Search a Spanish gaming-community archive and receive exact x402 page purchase URLs.
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.
Average 4.5/5 across 2 of 2 tools scored.
The two tools are clearly distinct: archive_catalog provides an overview of corpus coverage and counts, while search_archive performs actual searches. There is no overlap in their purposes.
Both tool names include 'archive', but one is noun-first (archive_catalog) and the other is verb-first (search_archive). Minor inconsistency, but the pattern is still readable and predictable.
With only two tools, the server feels thin, but for a narrow archive search purpose it is reasonably scoped. The count is at the borderline where it could be seen as minimal yet sufficient.
The server covers the core workflow of discovering archive contents (catalog) and searching with previews and purchase links. There is no direct post-fetch tool, but the external purchase URL likely satisfies that need, so gaps are minor.
archive_catalogInspect archive coverageAInspect free corpus coverage, dates, public sections, and available topic and post counts before searching or paying.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context about the specific data inspected (free corpus, dates, public sections, counts) and implies a paid tier exists, which goes beyond the annotation's safety profile.
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 a single sentence that front-loads the verb 'Inspect' and packs all key details without redundancy. Every word adds value, making it perfectly concise and well-structured.
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?
For a zero-parameter tool with an output schema and strong annotations, this description is complete. It states what will be inspected, when to use it ('before searching or paying'), and relies on the output schema to convey return values, which is sufficient.
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?
There are zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it appropriately focuses on the tool's purpose instead.
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 uses the specific verb 'Inspect' and clearly identifies the resource as 'free corpus coverage, dates, public sections, and available topic and post counts.' This distinguishes it from its sibling tool 'search_archive' which is for searching rather than inspecting.
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 phrase 'before searching or paying' provides explicit temporal guidance for when to use this tool. However, it does not explicitly name the alternative tool 'search_archive' or state when not to use it, so it falls slightly short of the highest rating.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_archiveSearch the Comrades of War archiveASearch 39,309 privacy-curated public posts from a Spanish Call of Duty clan, gaming community, and SA-MP role-play archive. Returns free previews and exact x402 purchase URLs. Use concise Spanish terms and pay only when a preview is relevant.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of free previews to return. | |
| query | Yes | Concise Spanish search terms, for example “servidor rust” or “historias roleplay”. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the tool as read-only, idempotent, and non-destructive, so the description adds value by revealing the archive size, the nature of results (free previews and purchase URLs), and the payment implication. This goes beyond what annotations provide, though it does not detail behaviors like pagination or sorting.
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 sentences, front-loaded with the core action, and every sentence adds substantive information. It avoids redundancy with the schema and annotations, making it highly efficient and well-structured.
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 presence of an output schema, the description does not need to explain return values in detail. It adequately covers the tool's purpose, result type, and usage guidance, and is complete enough for a search tool with two parameters. A slight gap is the lack of explicit comparison to the sibling archive_catalog, but this is likely covered by the sibling tool's own description.
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 input schema already provides thorough descriptions for both parameters (query with example, limit with meaning), yielding 100% schema coverage. The tool description adds context about using concise Spanish terms and the relationship between previews and payment, enriching the meaning of the parameters beyond the schema fields.
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 function with a specific verb ('Search') and resource (the Comrades of War archive), and distinguishes it from the sibling archive_catalog by emphasizing search over browsing. It also specifies the content type and the result format (free previews and purchase URLs), making its purpose unambiguous.
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 how to use the tool: it instructs using concise Spanish terms and notes to pay only when a preview is relevant. It does not explicitly mention when to use this tool instead of archive_catalog, but the search-focused nature implicitly differentiates it, so the context is clear though not exhaustive.
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.
No comments yet. Be the first to start the discussion!
Sign in to create a connector for this server.