Skip to main content
Glama

WhatsDownNow

Request a service be added

request_service

Ask WhatsDownNow to start monitoring a service that is not in the catalog yet. Humans can also do this at /request. Votes for the same name are counted together. Optional url helps us find the site; optional reason is noted. Optional email is only used to notify the requester when the service is added (double opt-in; never marketing). If the name already matches a tracked service, the live slug is returned instead of a new request.

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

Input Schema

NameRequiredDescriptionDefault
urlNoWebsite or official status page (optional)
nameYesService name, e.g. 'Linear' or 'mybank.com'
emailNoOptional address to notify when it's added (we send a confirmation link; never marketing)
reasonNoWhy this service should be added (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare a non-destructive write (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds meaningful context beyond them: votes for the same name are aggregated, email requires double opt-in and is never used for marketing, and duplicate names degrade to returning the existing slug. These disclosures cover privacy handling and deduplication behavior that the annotations do not. It does not address rate limits or whether the request triggers any immediate notification, so it falls just short of a 5.

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 short sentences, front-loaded with purpose and followed by parameter behavior; every sentence carries relevant information. Some content, particularly the email opt-in detail, partially duplicates the schema description, which keeps it from being maximally tight.

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?

With no output schema, the description usefully explains the return case (existing live slug when the name is already tracked), and it covers all optional parameters plus the deduplication model. For a write operation with open-world scope it provides adequate behavioral context, though it omits anything about submission limits or follow-up results.

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 a baseline of 3 applies, but the description adds value by explaining that name is the identity used for vote aggregation and that url/reason/email are all optional with specific purposes. The email double opt-in and never-marketing guarantee reinforce the schema's own note, adding intent rather than new syntax.

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 description opens with a specific verb and resource — asking WhatsDownNow to monitor a service not yet in the catalog — and implicitly distinguishes this mutation from catalog-reading siblings by scoping it to untracked services. It also names the human equivalent at /request, so the agent knows exactly what action is being taken.

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 clearly states the triggering condition (service is not in the catalog yet) and describes what happens when the name already matches a tracked service (the live slug is returned instead of creating a request), which effectively routes the agent away from duplicate submissions. It stops short of naming a sibling such as list_services to verify absence first, so the guidance is strong but not fully explicit about the check-then-request sequence.

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.