Still losing time to small decisions? Spin or Flip brings randomization into Claude so you can offload mental load to chance instantly.
Send a decision wheel to Spin or Flip and get a shareable spinning-wheel URL. Use this whenever a user wants to spin a wheel or make a random decision. Before calling this tool, generate the wheel yourself: pick a short title (2–6 words) and 6–12 options (1–4 words each) based on the topic. Optionally include a CSS linear-gradient background that matches the mood of the topic. Returns a URL the user can open to spin the wheel instantly.
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Short wheel title, 2–6 words (e.g. "Best Pizza Styles", "Weekend Activities") | |
| options | Yes | 6–12 options, 1–4 words each (e.g. ["Margherita", "Pepperoni", "BBQ Chicken"]) | |
| gradient | No | Optional CSS linear-gradient matching the topic mood (e.g. "linear-gradient(135deg, #f97316 0%, #ef4444 100%)") |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the return format (a shareable URL) and requires the caller to generate wheel content beforehand, but does not mention potential errors, rate limits, or data handling, which are relevant for an external service call.
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?
Three sentences, every sentence earns its place: what it does, when to use it, and how to prepare inputs. The most important information is front-loaded.
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 simple tool with 100% schema coverage and no output schema, the description adequately explains the return value and procedural steps. It could mention error scenarios or validation behavior, but the current level suffices for straightforward use.
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 description coverage is 100%, and the description largely restates the same constraints (title 2–6 words, options 6–12 items, 1–4 words each). It adds minor guidance about matching the topic mood, but does not substantially deepen understanding 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 opens with a specific verb+resource ('Send a decision wheel to Spin or Flip') and immediately states the output ('get a shareable spinning-wheel URL'). It clearly distinguishes this tool's purpose from any generic random-decision tool.
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?
Explicitly states when to use the tool ('Use this whenever a user wants to spin a wheel or make a random decision') and provides concrete pre-call instructions on generating the title, options, and optional gradient. No alternatives exist among siblings, so no exclusions are needed.
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!
Add one secure layer between your agents and this server.
Only one tool exists, so there is no risk of confusion between tools. The single tool's purpose is clearly defined.
With only one tool, naming consistency is not a concern. The name 'spinorflip' is descriptive but does not follow a verb_noun pattern, though it is not inconsistent.
A single tool for generating a spinning wheel is borderline thin but fits the narrow purpose. The server would benefit from additional tools for related actions (e.g., history, customization), but it remains functional.
The single tool fully covers the server's declared purpose: generating a shareable spinning wheel with user-provided title, options, and optional background. No obvious gaps exist for this domain.