Skip to main content
Glama

Recommend a StaffBots plan

recommend_plan
Read-onlyIdempotent

Recommend a StaffBots plan from business type, optional team size, and needs (dispatch, support, scheduling, lead follow-up, admin, reseller). Returns a rationale, checkout URL, and optional Human Supervisor add-on. Does not invent discounts.

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>"
    },
    "name": "recommend_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
needsNoNeeded roles or jobs: dispatch, support, scheduling, lead follow-up, admin, and/or reseller.
team_sizeNoTeam size as a number or a label like 'solo', 'small', or '15'.
business_typeYesWhat kind of business this is, e.g. delivery, logistics, home services, agency, reseller, or a short description.
wants_human_oversightNoSet true if they want a human reviewing exceptions.

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 establish readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description still adds value by promising a rationale, a checkout URL, and an optional Human Supervisor add-on, plus the 'does not invent discounts' honesty constraint. What it does not say is how the recommendation behaves for an unrecognized or ambiguous business type — a meaningful gap for a 4-parameter input.

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?

Three short sentences with the resource and inputs front-loaded, then outputs, then a guardrail — no filler. It is dense but readable; the final fragment 'Does not invent discounts' is terse enough to read as an afterthought even though it carries real behavioral weight.

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 no output schema, the description correctly discloses what comes back (rationale, checkout URL, optional add-on), which an agent needs. Combined with full parameter coverage and read-only annotations, only edge-case behavior (ambiguous business type, no matching plan) is left unaddressed.

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 every parameter is already documented with its accepted forms and examples. The description echoes the needs categories and the optionality of team size without adding format rules, defaults, or fallback behavior beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource ('Recommend a StaffBots plan') and lists the exact inputs it derives from (business type, team size, needs), so an agent can tell it is a recommendation engine rather than a catalog lookup. It does not name or distinguish itself from near-neighbors like list_plans/get_plan, leaving the differentiation implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrasing 'from business type, optional team size, and needs' implies the qualifying context (a prospect with known needs), which is real but indirect guidance. There is no explicit when-to-use/when-not statement and no reference to alternatives such as listing plans or comparing vendors, even though siblings like list_plans and get_plan exist.

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