Skip to main content
Glama

Managed Nerds

request_full_quote

Only after your user says yes to a full quote: send the estimate_id. A person at Managed Nerds replies by email within one business day.

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": {
      "estimate_id": "<estimate_id>",
      "user_approved": "<user_approved>"
    },
    "name": "request_full_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
timelineNo
estimate_idYes
contact_phoneNo
user_approvedYes
best_time_to_callNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare it is not read-only, not destructive, not idempotent, and closed-world. The description adds genuinely useful context beyond that: the response is human-mediated, arrives by email, and takes up to one business day. It does not warn that non-idempotent repeat calls may create duplicate quote requests, nor that contact details are handed to a person, which would be the meaningful next layer.

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?

Two short sentences with the gating condition front-loaded before the action, and a closing sentence on what happens next. No 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?

For a lead-submission tool with no output schema, the description covers intent, precondition, and response channel competently. But with six undocumented parameters and no statement of what a successful call returns or whether repeats are deduplicated, an agent still has to guess at the calling contract.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across six parameters, so the description carries the full burden. It explains only estimate_id and hints at user_approved via the 'says yes' framing; notes, timeline (the only enum), contact_phone, and best_time_to_call are left entirely undefined — their format and whether they are optional or required is unstated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action (send the estimate_id) and its result (a person at Managed Nerds replies by email), which is more concrete than a generic 'request' label. It implicitly separates itself from preliminary_estimate by insisting on the full-quote stage, though it never names that sibling.

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?

The precondition is unusually explicit: 'Only after your user says yes to a full quote,' which tells the agent when it may fire and implies an approval gate. What's missing is an explicit alternative — e.g., use preliminary_estimate or check estimate_status first — so the agent has to infer the comparison from sibling names.

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