Skip to main content
Glama

Final POS – Custom POS Builder

Create POS user

hub_create_user

Add a POS user — someone who signs in at the till with a PIN. Mirrors the cabinet’s "New POS user" form: first and last name, a 4-6 digit PIN, a role, optionally a phone. They get access to every outlet of the company, which update_user can narrow afterwards. BACK-OFFICE (Hub) users are NOT created here: those are invited by email from the cabinet, and that invitation flow is not available through this tool. If the merchant wants someone who can log in to the back office, say that and point them at Manage → Team → Users → Add User. The role decides what the new person may do, so PERMISSIONS ARE POWER. Confirm with the merchant first, naming the person and the role out loud ("give Maria the Manager role — yes?"), and never act on a role change you inferred rather than were asked for. The change is live on the next request: rights are re-read from the role every time, so no one logs out and no agent key stops working — including yours, if the change reaches your own account. A new user also counts against the company plan’s user allowance and the call is refused once it is used up.

Input Schema

NameRequiredDescriptionDefault
phoneNoPhone as the merchant said it, e.g. "+1 555 123 4567"
roleIdYesRole id from get_roles — required, and it decides their permissions
pincodeYesRequired — 4 to 6 digits, what they type at the till
lastNameYesRequired
firstNameYesRequired

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover readOnly/openWorld/destructive flags, so the description carries the real behavioral load: role assignment drives permissions, changes take effect on the very next request with no logout, the change can affect the caller's own account, and the call is refused once the plan's user allowance is exhausted. That is substantive context beyond the structured hints.

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?

Front-loaded with purpose, then exclusions, then warnings – good ordering. It is on the long side and the permissions paragraph drifts into role-change semantics ('no one logs out and no agent key stops working') that are only indirectly about creating a user, so it is not maximally tight.

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

Completeness5/5

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

For a non-destructive mutation with no output schema, the description covers everything an agent needs: what gets created, required fields, permission implications, confirmation protocol, quota refusal behavior, and where the sibling tools take over. Nothing material is missing.

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 are already documented, including the PIN pattern and the roleId/get_roles linkage. The description's field list ('first and last name, a 4-6 digit PIN, a role, optionally a phone') largely restates the schema, adding only the qualitative note that the role decides what the person may do. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Add a POS user') and immediately defines the resource by its distinguishing trait: signs in at the till with a PIN. It explicitly separates itself from back-office/Hub users and names the sibling (update_user) that handles outlet narrowing, so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (till user with PIN), when-not-to-use (back-office users are email-invited and 'not available through this tool'), an alternative (update_user for narrowing, cabinet Manage → Team → Users → Add User), and a procedural precondition: confirm the person and role with the merchant out loud first.

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.