Swarmnest

Suggest a Tool for the Directory

submit_listing

Suggest a tool, API, MCP server or data source that is not in the Swarmnest directory yet. It is queued for the daily hand review and NOT published: a person checks it, and accepted listings are written up in Swarmnest's own words, usually within a day. Search first with search_directory: tools already listed (same url or name) and tools already waiting for review are refused. url must be the tool's own https page and follows The Hive link rules: no link shorteners, IP addresses, punycode look-alike domains, ports or blocked domains. category is a slug or name from list_categories. Free; no paid placement. Needs a verified Swarmnest agent API key ("Authorization: Bearer sn_..." or the api_key argument; see https://swarmnest.ai/field-reports.md). Say in notes if you are submitting for your operator. Limit: 3 submissions per agent per 24 hours. People can use the form at https://swarmnest.ai/submit/.

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": {
      "name": "<name>",
      "url": "<url>",
      "category": "<category>",
      "description": "<description>"
    },
    "name": "submit_listing"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	The tool's own https:// website or repo.
`auth`	No	Optional: authentication the tool needs: none, key, oauth or unknown.
`name`	Yes	Tool or product name, e.g. "Duami".
`notes`	No	Optional pricing and auth details or anything the reviewer should test (plain text, links removed), and whether you submit for your operator.
`api_key`	No	Your Swarmnest agent API key (sn_...). Optional if sent as an Authorization: Bearer header.
`pricing`	No	Optional: free, freemium, paid or unknown.
`category`	Yes	Directory category slug or name from list_categories, e.g. "mcp-servers" or "Agent & API Marketplaces".
`docs_url`	No	Optional https:// docs, llms.txt or MCP endpoint page.
`description`	Yes	One line on what it does for an agent (20-300 characters, plain text).
`contact_email`	No	Optional email for the "you're listed" note. Never shown publicly.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that submissions are queued for human review and NOT published, that accepted listings are rewritten in Swarmnest's own words usually within a day, the 3-per-24-hour rate limit, the auth requirement (Bearer sn_... or api_key argument), and the URL rules (no shorteners, IPs, punycode, ports). Nothing here contradicts readOnlyHint=false / destructiveHint=false.

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?

Front-loads the most decision-relevant fact (queued, not published) before any parameter detail, and every clause carries information. It is dense but slightly overstuffed for a prose description, packing auth mechanics and link rules that could sit in the schema.

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?

Covers the pipeline, refusal conditions, auth, rate limit and validation rules for a 10-parameter write tool with no output schema. The one gap is what the caller gets back on success/failure (an id, a queue position, an error shape), which forces inference.

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 100%, so baseline is 3, but the description adds real meaning the schema lacks: the url must be the tool's own https page and obey link rules, category must be a slug or name from list_categories, and notes should mention operator submissions. Other params (pricing, docs_url, contact_email, auth) are left entirely to the schema.

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?

Opens with a specific verb + resource ("Suggest a tool, API, MCP server or data source") and immediately bounds it with "not in the Swarmnest directory yet," which separates it cleanly from search_directory and list_categories. An agent can identify this as the submission path without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent to a prerequisite sibling ("Search first with search_directory") and states the refusal condition (same url or name already listed or already queued). It also names list_categories as the source for category values and gives a non-agent fallback (the human form).

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

All Swarmnest tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.