Skip to main content
Glama

Request a StaffBots demo or walkthrough

book_demo_request

Collect a demo or walkthrough request (name, email, company, message, plan interest) and email it to hello@staffbots.ai. When email is not configured, the request is stored for the team instead.

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": {
      "name": "<name>",
      "email": "<email>"
    },
    "name": "book_demo_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe requester's name.
emailYesThe requester's email address.
companyNoCompany or trade name, if any.
messageNoWhat they want to see or ask.
plan_interestNoPlan they are interested in, if known: starter, dispatch, biab, reseller, or supervisor.

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?

The annotations declare readOnlyHint=false, openWorldHint=false and idempotentHint=false, and the description usefully adds the actual side effect (an email to hello@staffbots.ai) plus a graceful fallback where the request is stored when email is not configured. What it omits is what the agent actually receives back and the practical consequence of idempotentHint=false, namely that repeat calls create duplicate emails/records.

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 sentences: the action and destination come first, and the degraded-mode behavior follows. Every clause carries information an agent needs, and nothing is padded or repeated.

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

Completeness3/5

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

For a write-side-effect submission tool with no output schema, the definition covers inputs and the email destination but never says what a successful or failed call returns to the agent, nor how it relates to the sibling booking tool. Enough to call it, not enough to confirm success or choose confidently between demo paths.

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 all five parameters, including the plan_interest value set, are already documented in the schema. The description restates the field list and adds no format, validation, or intent guidance beyond it, 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 gives a concrete verb and resource: it collects a demo/walkthrough request with five named fields and emails it to hello@staffbots.ai. That is clear enough to act on without opening the schema, but it never distinguishes itself from the sibling book_demo_link, leaving an agent to guess which of the two demo paths to pick.

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: an agent can infer this is for users wanting a demo or walkthrough, and the field list hints at the qualifying details to gather. There is no explicit when-to-use, no exclusion, and no routing statement against book_demo_link or the plan-comparison tools.

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