Skip to main content
Glama

Report Missing Capability

report_missing_capability

Call this when the user wants something none of the other tools can do. Describe the goal and the kind of tool that would help in context. Doing so records the request for doola's team and changes nothing on the customer's account. It returns no new tools, so after calling it tell the user this isn't available here and point them to the doola dashboard.

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": {
      "context": "<context>"
    },
    "name": "report_missing_capability"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesYour goal and what kind of tool would help accomplish it. Describe it in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Output Schema

NameRequiredDescriptionDefault
messageNoAcknowledgement of the report.
conversation_idNoThis conversation's handle. Pass it unchanged as conversation_id on every later call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Optional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / conversation_id
      Added value: +{
      +  "description": "This conversation's handle. Pass it unchanged as conversation_id on every later call.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, which alone would leave the agent unsure whether the customer's data is mutated; the description resolves that ambiguity directly ('changes nothing on the customer's account'). It also pre-empts a false expectation about the return value ('returns no new tools') and states where the record goes, all beyond what annotations provide.

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 trigger condition, then the action, then the side-effect disclaimer, then the post-call instruction. Every sentence carries distinct information with no filler or repetition.

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 not be explained, yet the description still adds the crucial 'returns no new tools' caveat. Combined with the no-account-change statement and the user-facing follow-up script, an agent has everything needed to call this correctly and handle the result.

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 — including the privacy rule and the free-form nature of `context` — are already documented in structured data. The description restates the `context` instruction and implies the privacy constraint only indirectly; with the schema doing the heavy lifting, baseline 3 applies.

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 verb+resource — records a request for doola's team — and frames the trigger condition up front so the agent knows exactly what class of situation this tool serves. It explicitly distinguishes itself from every sibling by negation ('none of the other tools can do'), which is the strongest possible differentiation in a 12-tool sibling set.

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 the when ('user wants something none of the other tools can do'), the implicit when-not (any sibling handles it), and the follow-up action after the call ('tell the user this isn't available here and point them to the doola dashboard'). Nothing about selection or next steps is left to inference.

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.