Skip to main content
Glama

Ultimate Business Machines (no account)

Send a plan to UBM's team

ubm_request_plan
Destructive

Send a business's plan and contact details to UBM's team so they get in touch -- the Solutions guide's own 'send me this plan' form. Only call this when the person has asked to be contacted, with the details they gave you: their name and an email or phone number. UBM doesn't email the person automatically; the team replies. Limited to a few per day per network.

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": {
      "business_type": "<business_type>",
      "answers": "<answers>",
      "name": "<name>"
    },
    "name": "ubm_request_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
roleNo
emailNo
phoneNo
answersYesThe guide answers by question id (ubm_get_guide_questions): every question it marks required needs an answer (most take 'Not sure')
messageNo
businessNo
preferredNo
business_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructive, openWorld and non-idempotent, and the description adds real context beyond them: UBM does not email the person automatically and the team replies instead, so there is no immediate transactional response. It also discloses a rate constraint ('a few per day per network'), though 'a few' is imprecise and the consequence of hitting it is not stated.

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?

Three sentences, front-loaded with the action and outcome, then the call condition, then the behavioral caveats. No sentence repeats the title or the schema, and each adds a distinct fact.

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

Completeness4/5

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

With 9 parameters, a nested object, no output schema and a destructive annotation, the description covers purpose, precondition, contact requirements, follow-up behavior and rate limiting — enough to call it correctly and set expectations. The remaining gap is that the enum values and most optional fields are left entirely to the schema.

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 only 11% across 9 parameters, so the description must carry the load. It explains only name and the email/phone contact requirement, and the answers object is documented in the schema rather than the description. business_type, role, business, message and preferred are undocumented in either place, and the description does not say that email/phone are optional while business_type and answers are required.

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 and resource ('send a business's plan and contact details to UBM's team') plus the outcome ('so they get in touch'), and identifies itself as the Solutions guide's 'send me this plan' form. That framing cleanly separates it from siblings like ubm_quote_plan, ubm_recommend_plan, ubm_see_demo and ubm_start_signup.

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?

Gives an explicit gating condition: 'Only call this when the person has asked to be contacted' and requires the contact details the user supplied. That is a genuine when/when-not rule. It stops short of naming an alternative sibling for cases where the person is not ready to be contacted (e.g. ubm_quote_plan or ubm_see_demo).

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