Skip to main content
Glama

Get a StaffBots plan

get_plan
Read-onlyIdempotent

Get details for one StaffBots plan or add-on. Accepted values: starter, dispatch, biab (or 'business in a box'), reseller, supervisor (Human Supervisor add-on).

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": {
      "plan": "<plan>"
    },
    "name": "get_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesPlan or add-on name or slug: starter, dispatch, biab, reseller, supervisor, or a close alias.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that — the accepted value set and the alias mapping (biab = "business in a box", supervisor = Human Supervisor add-on) — but says nothing about error behavior for unknown names or what the returned "details" comprise.

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, no waste, with the core purpose front-loaded and the value enumeration following. Nothing could be removed without losing information.

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?

For a single-parameter read-only lookup with full annotation coverage this is nearly complete. The one gap is that no output schema exists, and "details" is never expanded, so an agent cannot anticipate the shape of the response.

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

Parameters4/5

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

Schema coverage is 100% and the schema already lists the valid values, so the baseline is 3. The description earns above baseline by decoding ambiguous values: 'biab' as "business in a box" and 'supervisor' as the Human Supervisor add-on, which the schema does not explain.

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 clear verb and resource: "Get details for one StaffBots plan or add-on." The word "one" implicitly contrasts with the plural-list siblings (get_plans, list_plans) but never names them, so differentiation is inferential rather than explicit.

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?

Usage is only implied by the singular scope; there is no statement of when to use this versus get_plans, recommend_plan, or compare_to. The enumeration of accepted values does help an agent decide the tool applies, but no exclusions or alternatives are given.

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