Skip to main content
Glama

Managed Nerds

request_callback

Only when your user asked: a callback from a person at Managed Nerds (not a booking; they confirm a time by email within one business day). Needs the buyer's name, email and phone, and up to 3 windows on Monday to Friday, 8am to 6pm Eastern. Send estimate_id to attach it to an estimate.

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": {
      "contact": "<contact>",
      "user_approved": "<user_approved>"
    },
    "name": "request_callback"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
topicNo
contactYes
windowsNo
businessNo
time_zoneNo
estimate_idNo
user_requestNo
user_approvedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world request; the description adds real substance on top: human follow-up by email within one business day, availability limited to Monday–Friday 8am–6pm Eastern, and a maximum of 3 proposed windows. It omits what the caller receives back or what happens if no window fits, which keeps it 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?

Dense and front-loaded: the gating condition and the nature of the callback come first, then required data, then the optional estimate linkage. The opening fragment 'Only when your user asked:' is slightly clipped but still parses cleanly, and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the essentials for a mutating request tool: permission gating, required contact fields, window limits and time zone framing. However, with no output schema and no parameter descriptions, the four unexplained parameters (business, topic, notes, time_zone) and any expected confirmation response leave the definition short of complete.

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?

With schema description coverage at 0% across 9 parameters, the description compensates for the most important ones: contact must include buyer name, email and phone, windows are capped at 3 within weekday business hours, and estimate_id attaches the request to an estimate. It leaves notes, topic, business and time_zone entirely unexplained, which is a meaningful gap given the nested objects and zero schema documentation.

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 and resource (a callback from a person at Managed Nerds), and explicitly scopes it as not a booking, so an agent can distinguish it from request_service or ask. The parenthetical clarifying that a human confirms a time by email makes the outcome unambiguous.

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?

Provides an explicit gating condition ('Only when your user asked'), which pairs with the required user_approved flag and rules out speculative calls. It does not name a concrete alternative tool for the booking case, so guidance is clear but not fully comparative.

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