Bespoke cricket travel specialist with two decades of experience. Search tours, explore destinations, check match schedules, and submit enquiries. Covers IPL, Ashes, World Cups across India, South Africa, Australia, Sri Lanka, Bangladesh, and the West Indies. AI-powered, no authentication required.
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.7/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined.
With a single tool, naming consistency is not a issue. The name 'get_about' follows a clear verb_noun pattern.
The server claims to represent a tour service but provides only one informational tool. This is too few for the apparent scope, leaving core travel-related operations missing.
The server lacks any tools for browsing tours, making bookings, or managing itineraries, which are essential for a tour service. The single tool provides only basic company information.
get_aboutAInspectGet information about Follow On Tours — who we are, how we work, our experience, and how the bespoke cricket travel service operates. Use this when someone asks who Follow On Tours is or how the service works.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the informational nature of the tool (returning details about the company) and implicitly signals it is a read-only, non-destructive operation. It could optionally mention that no parameters are needed or that it returns static information, but the current text is adequate for a simple informational tool.
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 sentences. The first sentence states the core function and content scope; the second provides usage guidance. Every word earns its place, with no fluff or repetition. The structure is front-loaded with the verb and resource.
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 (no parameters, no output schema, no siblings), the description is fully complete. It tells the agent what the tool does, what content it covers, and when to invoke it. There are no gaps that would leave an agent uncertain about using this tool correctly.
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 no parameters, so the baseline is 4. The description adds context about what information will be delivered, which compensates for the absence of parameter explanations. The schema shows no properties, and the description clarifies the tool's output content, making it semantically clear.
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 purpose: 'Get information about Follow On Tours' and enumerates specific content areas ('who we are, how we work, our experience, and how the bespoke cricket travel service operates'). This provides a specific verb + resource with concrete detail, making it easy to distinguish from any potential alternative.
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 explicitly states when to use: 'Use this when someone asks who Follow On Tours is or how the service works.' This gives direct guidance on usage scenarios, fulfilling the need for when-to-use instructions even without sibling tools to contrast against.
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!
