Skip to main content
Glama
Sign In

LaunchDistro

by com.launchdistro
OverviewDiscussionsAdmin

Where the product qualifies

match_directories
Read-only

Every catalogued directory for this product: ready, locked (a Launch or Pro opens it), no tested playbook yet, or not a fit, each with the reason (product type, region, badge answer).

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": "match_directories"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNoThe product's website or name. Leave empty for the product last worked on (list_products shows them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful output semantics (the four status categories and their reasons like product type, region, badge answer) but does not describe return format, pagination, or other behavioral traits.

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?

The one-sentence description is compact and front-loads the scope with the status categories. The parentheticals are slightly dense but every clause carries information.

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?

For a read-only tool with one parameter and no output schema, the description gives the essential output categories but leaves some ambiguity around what 'ready' or 'locked' means and how the list is structured. It is adequate but not fully complete.

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?

The single parameter `product` has a complete schema description (100% coverage), including the default behavior when empty. The description adds no parameter information beyond the schema, so the baseline of 3 is appropriate.

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 lists the categories of directories returned (ready, locked, no playbook, not a fit) with reasons, which conveys the tool's scope. However, it lacks a clear action verb and does not differentiate from siblings like suggest_directory or list_submissions, so it is clear but not maximally specific.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as suggest_directory or list_submissions. The description only implies it is for retrieving a product's directory statuses but does not state conditions, exclusions, or alternatives.

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

All LaunchDistro toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources