Skip to main content
Glama

Managed Nerds

preliminary_estimate

Only when your user asked: a preliminary monthly estimate for managed IT (service_model managed; IT support time is billed separately, with an optional pre-paid block) or co-managed security (a range before volume discounts, not an offer) for a US business under 50 seats. Needs the buyer's name, business and email, and what they asked for. Body as in /agent/openapi.json (EstimateRequest).

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>",
      "business": "<business>",
      "user_request": "<user_request>",
      "user_approved": "<user_approved>"
    },
    "name": "preliminary_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
rmmNo
usersNoAll licensed Microsoft 365 or Google Workspace users in the tenant: ITDR is all or nothing
tenantNo
contactYes
revisesNoRevise an earlier estimate: its estimate_id (with status_token)
supportNoManaged IT only: a pre-paid block of support hours. Send hours_per_month, or non_technical_users for our suggestion (half an hour a month each).
businessYes
servicesNo
computersNo
status_tokenNoThe token from the earlier estimate's status_url
user_requestYes
service_modelNo
user_approvedYes
also_interested_inNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations declare non-read-only, non-idempotent, non-destructive, non-open-world, so the write nature is already conveyed. The description adds genuinely useful non-annotation context: IT support time is billed separately, the figure is a range before volume discounts and is not an offer. It omits what happens on submission, whether it creates a record, or what the response contains, which is a real gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The gating condition is correctly front-loaded, but the opening sentence is a long parenthetical-laden chain that mixes the purpose, pricing caveats, and eligibility scope. Referring the agent to an external file for the body rather than summarizing the key fields costs the agent a lookup.

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

Completeness2/5

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

With 14 parameters, nested objects, no output schema, and low schema coverage, this definition should carry far more weight. Directing the agent out to /agent/openapi.json (EstimateRequest) is a deferral, not a description, and there is no guidance on the required user_approved flag or the revises/status_token revision flow.

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 description coverage is only 29% across 14 parameters, so the description must compensate and mostly does not. It mentions the buyer's name, business, email, and what they asked for, mapping to contact, business and user_request, and it gestures at service_model and the support block; but computers, tenant, services, rmm, revises and status_token semantics are left entirely to an external openapi.json pointer.

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?

States a specific verb+resource: a preliminary monthly estimate for managed IT or co-managed security, scoped to a US business under 50 seats. It clearly distinguishes itself from request_full_quote and request_callback by calling the output preliminary and 'not an offer'. It is slightly diffuse because it packs pricing caveats and a schema pointer into the same sentence as the purpose.

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?

Opens with an explicit gating condition ('Only when your user asked') and scopes it to under-50-seat US businesses, which tells the agent when not to use it. It does not name the sibling to use instead when the gate fails (e.g. request_full_quote or check_fit), leaving the alternative 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.

Resources