LaunchDistro

Report what a directory said

report_directory_fact

When a directory shows something its playbook did not say, report it in the page's own words: how long approval takes, whether the free link is dofollow, whether a free route still exists, a badge or link-back rule, a price, a changed form. One fact per report: when a directory has become paid only, send free_route no as well as the price. It goes straight to LaunchDistro for review (the user does not need to email anyone) and improves the catalog for everyone. Stored with the user's account in case we need to ask; only the directory fact is used.

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>",
      "kind": "<kind>",
      "value": "<value>"
    },
    "name": "report_directory_fact"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes
`quote`	No	The page's exact words that state it, copied, never paraphrased.
`value`	Yes	The fact: approval_time in days ("120"), free_link one of dofollow\|nofollow\|badge\|top3\|none (the link a free listing gets), free_route yes or no (can a listing still be had for free; needs quote and source_url), badge one of required\|for_dofollow\|none, price in dollars ("19"); otherwise a short description. A value in another form is refused.
`directory`	Yes	The directory's slug.
`source_url`	No	The directory's own page those words are on.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

changedInput schema / properties / kind / enum

Previous value: -[
-  "approval_time",
-  "free_link",
-  "badge",
-  "price",
-  "form_changed",
-  "other"
-]New value: +[
+  "approval_time",
+  "free_link",
+  "free_route",
+  "badge",
+  "price",
+  "form_changed",
+  "other"
+]

changedInput schema / properties / value / description

Previous value: -"The fact: approval_time in days (\"120\"), free_link one of dofollow|nofollow|badge|top3|none, badge one of required|for_dofollow|none, price in dollars (\"19\"); otherwise a short description."New value: +"The fact: approval_time in days (\"120\"), free_link one of dofollow|nofollow|badge|top3|none (the link a free listing gets), free_route yes or no (can a listing still be had for free; needs quote and source_url), badge one of required|for_dofollow|none, price in dollars (\"19\"); otherwise a short description. A value in another form is refused."

First observedNov 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate a non-read-only, non-destructive, non-idempotent write. The description adds meaningful behavior: reports go straight to LaunchDistro for review, the user does not need to email anyone, the report is stored with the account, and only the directory fact is used. It still does not explain duplicate handling or the success/failure response.

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 front-loads the trigger and examples, then states the one-fact constraint, review flow, and storage policy. The opening sentence is dense, but every clause supplies useful reporting context and there is no filler.

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

Completeness4/5

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

For a five-parameter tool with no output schema, it covers purpose, trigger, data handling, and the key paid-only cross-field case. The remaining gaps are response behavior, duplicate handling, and explicit sibling-tool routing.

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

Parameters4/5

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

Schema coverage is 80%, so the schema already documents most parameters. The description adds cross-field guidance: quote must be the page's exact words, one fact per report, and a paid-only directory should also send free_route no along with the price. That is useful but modest beyond the detailed schema descriptions.

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?

Uses a specific verb, 'report', and a specific resource, 'directory fact', scoped to facts a directory playbook did not state. It lists concrete examples such as approval time, free link, free route, badge, price, and changed form, so an agent can distinguish this from reading a playbook or recording a 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?

Gives an explicit trigger: when a directory shows something its playbook did not say. It also adds the one-fact-per-report constraint and a special paid-only case, but it does not name sibling alternatives such as suggest_directory or verify_link or say when not to use this tool versus them.

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

All LaunchDistro tools Inspect

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.