Skip to main content
Glama
Sign In

LaunchDistro

by com.launchdistro
OverviewDiscussionsAdmin

Playbook for one directory

submission_playbook
Idempotent

How to submit to one directory: what its form asks, which profile field goes where, the fields the profile lacks, the free plan's conditions, and where to stop. Call it before every submission. Counts as one submission attempt (a same-day re-read is free). Refused, and not counted, for a directory that is not a fit for the product.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "directory": "<directory>"
    },
    "name": "submission_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNoThe product's website or name. Leave empty for the product last worked on (list_products shows them).
directoryYesThe directory's slug (from match_directories or plan_submissions).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, non-open-world behavior. The description adds important behavioral context beyond annotations: it counts as one submission attempt, same-day re-reads are free, and unfit directories are refused without being counted.

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

Conciseness5/5

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

The description is front-loaded and compact. Every sentence contributes: the first explains the playbook contents, the second gives the call timing, and the remaining sentences explain attempt counting and refusal behavior.

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

Completeness5/5

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

With two simple parameters fully described in the schema and no output schema, the description provides enough context by enumerating what the playbook contains and when it is refused. An agent has what it needs to decide and call correctly.

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 the directory and product parameters are already fully documented in the schema. The description does not add parameter-level meaning beyond that baseline.

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

Purpose5/5

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

The description states a specific resource and purpose: a per-directory submission playbook covering form fields, profile mapping, missing fields, free-plan conditions, and stopping points. It also distinguishes itself from record_submission by saying to call it before every submission.

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

Usage Guidelines4/5

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

It gives clear usage timing ('Call it before every submission') and a refusal condition ('for a directory that is not a fit for the product'). It does not explicitly name alternative tools such as match_directories or record_submission, but the surrounding context makes the workflow clear.

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