launch-record-lookup
Server Details
Look up a domain's public Website Launches launch record, owner verification & trust context.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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.5/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion. The tool's purpose is clearly distinct.
The single tool name 'lookup_launch_record' follows a clear verb_noun pattern, and consistency is trivially perfect.
The server is narrowly scoped to looking up a single launch record; one tool is perfectly appropriate for this focused purpose.
The tool fully covers the declared functionality of looking up a launch record for one domain, with no missing operations within its scope.
Available Tools
1 toollookup_launch_recordLook up a launch recordARead-onlyInspect
Look up the public Website Launches launch record for a single domain. Returns launch timing, owner verification status, milestone summary, public trust context, and a public record URL. Single domain only; does not search, list, discover, or export websites. Hosting, registrar, and location are secondary details — only surface them if the user explicitly asks.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | A single website domain or URL, such as example.com or https://www.example.com/about. Provide exactly one domain — not a list, and not a search query. |
Output Schema
| Name | Required | Description |
|---|---|---|
| domain | No | |
| status | Yes | |
| owner_status | No | |
| public_links | No | |
| launch_record | No | |
| trust_context | No | |
| basic_identity | No | |
| technical_details | No | |
| recommended_response | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by clarifying the single-domain constraint and the behavior on secondary details. It does not contradict annotations and provides operational context beyond the annotations.
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?
Two sentences, front-loaded with action and return value. Every word is meaningful. No redundancy or filler. Efficient and clear.
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 one simple parameter, existing output schema, and annotations covering safety, the description is complete. It tells the agent exactly what to expect and how to use the tool without missing information.
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 single parameter 'domain' is fully covered in the schema description (100% coverage). The description reinforces the constraint of exactly one domain but does not add new semantic detail beyond the schema. Baseline 3 is appropriate.
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 it looks up a launch record for a single domain and lists what it returns (launch timing, verification status, etc.). It explicitly distinguishes from non-supported actions like searching or listing. The title 'Look up a launch record' is specific and aligned.
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 'Single domain only' and lists what the tool does not do (search, list, discover, export). Also provides guidance on secondary details: only surface them if the user explicitly asks. This gives clear context for when and when not to use.
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!