Skip to main content
Glama

agentswitchboard

Request a Missing Tool

request_missing_tool

Tell the Agent Switchboard maintainer that the directory has nothing for a job. Use it after search_agents (and a task or category, if one fits) found nothing that does what the user needs. The request is recorded privately and read in the weekly review, which uses requests to decide what to look for and add; nothing is published, no issue is opened, and there is no reply. Describe the job, never the user: no names, emails, company details or conversation. Limited to 10 requests per hour per caller.

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": {
      "need": "<need>"
    },
    "name": "request_missing_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesThe job no listing does, in plain words (10–500 characters), e.g. "an MCP server that files expense reports in Expensify". Describe the job, not the user.
triedNoThe search words that found nothing, if any
accessNoHow the agent needs to reach it: api, mcp, cli, browser-extension
categoryNoClosest category slug from list_categories, if any

Output Schema

NameRequiredDescriptionDefault
statusYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses the full lifecycle: recorded privately, read in a weekly review, used to decide what to look for, nothing published, no issue opened, no reply. It also states a concrete rate limit of 10 requests per hour per caller. This is exactly the context the readOnlyHint=false / openWorldHint=false flags cannot convey.

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?

Four tight sentences, front-loaded with purpose then trigger, then behavior, then content and rate constraints. The privacy instruction appears in both the description and the schema, a minor redundancy, but nothing else is wasted.

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?

An output schema exists, so return values need no explanation, and the description covers everything else an agent needs: when to call, what happens after, that no reply arrives, what not to include, and the rate cap. Nothing material is left ambiguous for a single-mutation request tool.

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 already 100%, so the baseline is 3, but the description adds specificity about what belongs in the required 'need' field: describe the job, never the user, with concrete exclusions (names, emails, company details, conversation). That privacy constraint is stricter than the schema's shorter note and shapes how the parameter should be filled.

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 first sentence names a specific actor (the Agent Switchboard maintainer), a specific action (tell them the directory has nothing), and the resource (a request for a missing tool). It is immediately distinguishable from search_agents, which it references, and from listing-submission tools by framing this as reporting a gap rather than adding an entry.

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 states a clear trigger: use after search_agents (plus a task or category filter) returned nothing that does the job, which is an explicit when-to-use condition. It does not explicitly contrast with submit_listing, so an agent must infer that a known-but-unlisted tool goes to submit_listing rather than here.

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.