Skip to main content
Glama

Add a staff member

add_staff

Adds a person customers can book with. They do all services unless service_ids is given. Not for restaurants. Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>",
      "name": "<name>"
    },
    "name": "add_staff"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFirst name is enough, e.g. "Maria".
addressYesThe venue’s address name, the "name" in name.bookare.app.
access_keyYesThe venue’s access key.
service_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, idempotent=false, destructive=false), the description discloses the important default that the person is assigned to all services unless service_ids is supplied, plus the single-venue scoping requirement. It omits duplicate handling and what the response contains, which is a minor residual gap for a write tool.

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?

Four short sentences, front-loaded with the core action and the service-assignment default before the eligibility caveat. No filler wording at all.

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 four-parameter mutation with no output schema, the description covers action, scope, default side effect, and an exclusion. It stops short of stating permission/auth expectations explicitly or what happens on a duplicate name, so it is not fully complete.

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 75%, with service_ids carrying no description in the schema; the description supplies exactly that missing meaning by explaining its default-all behavior. The venue/access-key pairing is also restated in plain terms, adding framing rather than pure duplication.

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 concrete verb and resource ('Adds a person customers can book with') and scopes it ('Acts on one venue'), which is more specific than the bare title. It doesn't explicitly contrast with the closest sibling add_instructor, so the agent must infer the staff-vs-instructor split.

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?

It gives one explicit exclusion ('Not for restaurants'), which is genuinely useful eligibility guidance. However, no positive preconditions or named alternatives are offered for cases like adding a class teacher, so the when-to-use routing is only partly covered.

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