Skip to main content
Glama

FoxAPIs data sources

Launch directories

launch_directories
Read-onlyIdempotent

The live list of places to launch a product: name, address, price model, review wait and backlink type, optionally for one category. Costs 1 credit a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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

Input Schema

NameRequiredDescriptionDefault
limitNoFor example: 5
categoryNoFor example: AI tools, dev tools, general launch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuinely new operational context the annotations cannot convey: a 1-credit cost per call, no charge for empty answers, and an API-key requirement. That billing/auth information is exactly the kind of disclosure that matters for an agent deciding whether to call.

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?

Three tight sentences with no filler, and the resource definition plus returned fields are front-loaded. Cost and auth details follow compactly; nothing is redundant despite the density.

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?

For a two-parameter, no-required-argument lookup with no output schema, the description covers what the tool returns, the cost model, and the auth requirement. An agent has everything needed to call it correctly and to judge whether the credit spend is worthwhile.

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 coverage is 100%, so the schema already documents both limit and category, so the baseline is 3. The description adds that the category filter is optional and accepts a single category, but says nothing about limit behavior or caps beyond what the schema states.

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 live list of places to launch a product" names a specific resource, and the description enumerates the fields returned (name, address, price model, review wait, backlink type). An agent can tell this is a directory/lookup tool distinct from the entity-lookup siblings, though the action verb (list/retrieve) is only implicit.

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?

It notes the category filter is optional but never says when to reach for this tool versus another, nor any prerequisites or exclusions. The launch-context framing implies usage, but no explicit when/when-not guidance or named alternatives are provided.

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