Skip to main content
Glama

Launch readiness checklist

toolfound_launch_readiness
Read-onlyIdempotent

Check whether an editable product draft has the fields needed for a complete directory submission. Returns an evidence-bounded result and the canonical web tool URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "toolfound_launch_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoYour product's public name as it should appear in a directory listing.
logoURLNoPublic HTTPS address of the logo image directories will show. Must be reachable without login.
taglineNoOne-line summary of what the product does and for whom.
websiteUrlNoPublic HTTPS address of the product's website or landing page.
descriptionNoOriginal description written for this listing, covering the problem, audience, workflow and limits. Short drafts are flagged as incomplete.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
linksYes
errorsNo
summaryYes
sectionsYes
canonical_result_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"Original description written for this listing, covering the problem, audience, workflow and limits. Short drafts are flagged as incomplete."
    • addedInput schema / properties / logoURL / description
      Added value: +"Public HTTPS address of the logo image directories will show. Must be reachable without login."
    • addedInput schema / properties / name / description
      Added value: +"Your product's public name as it should appear in a directory listing."
    • addedInput schema / properties / tagline / description
      Added value: +"One-line summary of what the product does and for whom."
    • addedInput schema / properties / websiteUrl / description
      Added value: +"Public HTTPS address of the product's website or landing page."
  2. Added

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are 'evidence-bounded' and that a canonical web tool URL is returned, which is useful, but it never says whether missing fields produce an error or a gap list, nor that all five inputs are optional so partial drafts can be checked — a key behavioral fact for a checklist tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core purpose front-loaded; nothing is redundant. 'Evidence-bounded' is slightly jargon-ish but does signal that the check will not speculate beyond supplied data.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations, a full-schema-coverage input schema, and an output schema, the minimum is met. The remaining gap is workflow context: an agent cannot tell from this description whether partial drafts are acceptable or what to do after a failed check, which matters for a zero-required-parameter validation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each of the five fields (name, logoURL, tagline, websiteUrl, description) is already well documented in the schema, including length limits and the note that short drafts are flagged. The description adds nothing parameter-specific beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and object: check an editable product draft for the fields required by a complete directory submission. That distinguishes it from submission or review siblings by intent, though it never names toolfound_launch_review or toolfound_submit_product to make the boundary explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Pre-submission validation is strongly implied by 'fields needed for a complete directory submission', but there is no explicit when-to-use, when-not-to-use, or pointer to the sibling (launch_review, submit_product) that would handle the next step. The agent must infer the position in the workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources