Reserve a paid AI consultation with Akshay Shetty; returns a Stripe payment link.
List available 60-minute paid AI-consultation slots with Akshay Shetty (EUR 500, timezone Europe/Tallinn). Returns ISO-8601 UTC start times to pass to request_consultation.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description provides all behavioral context: slots are 60-minute, paid, with a specific person, and returns ISO-8601 UTC times. It does not specify if the list changes frequently or if there are limits, but it is adequate.
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 essential information. No redundant words, and 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 no parameters, no output schema, and a simple list operation, the description is complete. It explains the purpose, prerequisites (who, price, timezone), and output format, enabling correct invocation and follow-up.
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 description naturally covers the parameter aspect. It adds meaning beyond the empty schema by specifying the slot characteristics.
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 specifies the exact action (list), the resource (60-minute paid AI-consultation slots with Akshay Shetty), and key details (price, timezone, output format). It clearly distinguishes from the sibling tool 'request_consultation'.
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 the tool should be used before 'request_consultation' by noting that it returns start times to pass to that tool. However, it lacks explicit guidance on when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Reserve a consultation slot and get a secure Stripe payment link. The booking is only CONFIRMED once the human completes the EUR 500 payment at the returned checkout_url — nothing is charged automatically and an unpaid hold expires in ~30 minutes.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Full name of the person booking | |
| tier | No | Consultation type: 'strategy' = AI strategy & sovereign automation (EUR 500); 'coaching' = life/personality/health coaching (EUR 200). Defaults to strategy. | |
| Yes | Contact email (confirmation is sent here) | ||
| notes | No | Optional: what you'd like to discuss | |
| client_tz | No | Optional IANA timezone of the person, e.g. Europe/London | |
| slot_start | Yes | An ISO-8601 UTC slot_start from list_consultation_slots, e.g. 2026-07-01T09:00:00Z |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description fully covers behavioral traits: nothing is charged automatically, payment is required via the returned checkout_url, and unpaid holds expire in ~30 minutes. This is comprehensive for a booking 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 two concise sentences with no fluff. It front-loads the action and key constraints, making it easy to scan.
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 6-parameter tool with no output schema, the description covers the critical workflow: payment link, expiration, and confirmation requirement. The return value (checkout_url) is mentioned, and the behavioral details are 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?
Schema coverage is 100%, so baseline is 3. The description adds context for 'tier' (different prices and types) and 'slot_start' (must be from list_consultation_slots), but does not elaborate on other parameters. It meets the baseline adequately.
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 reserves a consultation slot and provides a Stripe payment link, with explicit distinction from sibling 'list_consultation_slots'. The verb 'reserve' and resource 'consultation slot' are precise.
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 explains the workflow: choose a slot from list_consultation_slots, then book via this tool. It clarifies that booking is confirmed only after payment and that unpaid holds expire. It could explicitly state when not to use, but the context is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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!
Stripe payments for AI agents. Create links, verify, manage customers.
United States payments for AI agents — Stripe checkout via Stripe. Never holds funds.
Buy 15 minutes of Alex Finger's time, or an AI Repellent certificate. Agents only.
The checkout your AI runs — bumps, upsells, subscriptions, tax and affiliates on your own Stripe.
Add one secure layer between your agents and this server.
The two tools have clearly distinct purposes: one lists available slots, the other reserves a slot and provides a payment link. There is no ambiguity.
Both tools follow a consistent verb_noun pattern (list_consultation_slots and request_consultation), making the purpose clear at a glance.
With only 2 tools, the surface is minimal, but it fits the narrow domain of booking a single consultation service. Slightly under but reasonable.
The tools cover listing and reserving slots, but lack cancellation, status checking, or manual payment handling beyond the link. Notable but not critical gaps for this domain.
