Skip to main content
Glama

Invite a cashier

invite_cashier

Invites a cashier by email for one or more branches; Loyal Digicard emails the invite (valid 7 days). The Free plan includes 1 cashier (invites count).

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

Input Schema

NameRequiredDescriptionDefault
emailYesThe cashier’s email
branch_idsYesBranches the cashier may stamp at (list_branches)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world mutation, so safety is covered. The description adds genuinely new behavior: the platform sends the invite email, the invite expires in 7 days, and invites count against the Free plan's 1-cashier allowance. It does not say what happens on a duplicate or re-invite, which is the main remaining gap.

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, front-loaded with the action and mechanism, then the expiry and plan-limit facts. Nothing is redundant or padded.

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 two-parameter mutation with full schema coverage, no output schema, and annotations covering the safety profile, the description supplies the operationally important facts (email delivery, 7-day validity, plan limit). Only duplicate-invite and failure behavior are unaddressed, which is minor.

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 coverage is 100% and both parameters carry descriptions, so the schema does the heavy lifting, including pointing at list_branches for branch IDs. The description's 'by email for one or more branches' only restates what the schema already states, so baseline 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 pairs the specific verb 'Invites' with the resource 'a cashier', and adds the mechanism (email) and scope (one or more branches). An agent can tell this apart from revoke_cashier or list_team from the description alone. It stops short of explicitly naming a sibling to route away from, which keeps it at 4.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The only decision-relevant hint is the Free-plan limit of 1 cashier, which is a constraint rather than usage routing.

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