Skip to main content
Glama

Whizbrew

Request missing data

request_tool

Call this ONLY when search_tools found no tool that fits what the user asked; never when a tool fits. It passes the request to the Whizbrew team, who read every one to see what they can add. Free; no promise and no answer comes back, so tell the user it was passed on and go on by other means. Never put a key or password in it.

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": {
      "request": "<request>"
    },
    "name": "request_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesWhat the user asked for, in plain words (up to 1000 characters)
platformNoThe platform or site it is about, if any
searchedNoThe search_tools query that found nothing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/destructive flags; the description adds what the annotations cannot: the request is free, no answer is returned, a human team reads it, and credentials must never be included. It also tells the agent what to say to the user afterward.

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?

Four short sentences, front-loaded with the ONLY condition, then outcome, cost, and safety. No filler; each sentence carries a distinct, actionable fact.

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 three-parameter submission tool with no output schema, the description covers trigger, cost, expected outcome (no response), follow-up behavior, and a data-safety warning, so an agent can call it correctly and report back accurately.

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 description coverage is 100%, so all three parameters are already documented. The description adds only one semantic constraint on content (never put a key or password in it), which is useful but minimal beyond 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?

States a specific action (passes a request to the Whizbrew team) and its trigger (search_tools found nothing), which cleanly separates it from the sibling search_tools and call_tool.

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?

Gives an explicit exclusive condition ('ONLY when search_tools found no tool that fits') plus an explicit exclusion ('never when a tool fits'), leaving nothing to infer about routing.

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