Skip to main content
Glama

Get a StaffBots checkout link

get_checkout_link
Read-onlyIdempotent

Return the StaffBots signup URL for starter, dispatch, biab, or reseller. Signup opens a Stripe Checkout session from the plan price when billing is configured. If it is not, the buyer books a demo or emails hello@staffbots.ai. Human Supervisor has no public payment link.

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_checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesPlan slug or name: starter, dispatch, biab, reseller, or supervisor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, and the description adds real context: the URL opens a Stripe Checkout session priced from the plan and depends on billing being configured. It does not say what the response looks like when no link exists (error vs null vs demo URL), which is the key behavioral gap.

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?

Four short sentences with the primary outcome front-loaded and the conditional branch following in logical order. Every sentence contributes; only the email address / demo sentence is arguably verbose padding.

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 tool with no output schema, this covers the action, valid inputs, the conditional branch, and the key exclusion. The only missing piece is the shape of the return value on the no-link path.

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 plan slugs, so the baseline is 3. The description earns an extra point by clarifying that 'supervisor' is accepted by the schema but yields no payment link, meaning it adds meaning not present in the parameter description.

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 and resource ('Return the StaffBots signup URL') and enumerates the plans that resolve to a link. It does not explicitly route against siblings such as book_demo_link or get_plan, but the scope is unambiguous on its own.

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 the condition under which a link is produced (billing configured) and what happens otherwise (book a demo or email hello@staffbots.ai), plus the exclusion that Supervisor has no public payment link. It stops short of naming the sibling tool to call for the fallback path.

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