Skip to main content
Glama

agentswitchboard

Submit a Listing

submit_listing
Destructive

Suggest a new listing for the Agent Switchboard directory. This opens a PUBLIC GitHub issue that the maintainer reviews by hand; it does not publish anything. Use it only when the user asks to submit or list a product, after you show them the name, URL, and description you will send and they agree. Call search_agents first: if the product is already listed, tell the user instead. Limited to 5 submissions per hour per caller and one per URL per day. Not safe to retry blindly: each call that returns status "filed" opens a new issue.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe product's own homepage, docs, or GitHub repo (https)
nameYesProduct name, e.g. "Acme MCP"
accessNoHow agents reach it: api, mcp, cli, browser-extension
categoryNoSuggested category slug from list_categories
descriptionYesWhat it does and who it is for, in plain words (20–1500 characters)
contact_emailNoOptional. Sent privately to the maintainer for follow-up, never posted. Only include an address the user gave you for this purpose.

Output Schema

NameRequiredDescriptionDefault
statusYes
messageYes
issueUrlNo
existingSlugNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

The annotations already declare destructiveHint=true and idempotentHint=false, but the description adds substantial context beyond them: a PUBLIC GitHub issue is created, the maintainer reviews by hand, nothing is published, quotas of 5/hour and one per URL/day apply, and a "filed" status means a new issue exists so blind retries duplicate work. That is exactly the behavioral detail an agent cannot get from the structured fields.

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?

Under 90 words, front-loaded with what the tool does and what it does not do, then pre-conditions, then constraints. Every sentence carries distinct operational information; none restates the title or schema.

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?

Safety profile is covered by annotations, return format by the output schema, and the description supplies the remaining gaps: side-effect nature (public issue), dedupe prerequisite, user-confirmation gate, rate limits, and retry hazard. Nothing material to a correct invocation is missing.

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 workflow meaning to the three required fields by requiring the agent to echo name, URL, and description back to the user for approval before calling. It does not discuss the optional fields (access, category, contact_email), which the schema already covers adequately.

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?

Names a specific verb and resource ("Suggest a new listing for the Agent Switchboard directory") and immediately disambiguates the outcome: it opens a public GitHub issue for manual review rather than publishing. That distinction separates it cleanly from the read-oriented siblings like search_agents and list_categories.

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?

Explicit trigger ("only when the user asks to submit or list a product"), a mandatory pre-condition (show the user name/URL/description and get agreement), and a required prior step ("Call search_agents first: if the product is already listed, tell the user instead"). It even states the rate limits and the when-not-to-retry condition.

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.