list_accounts
Show which accounts are signed in, per restaurant, and which one is active. Useful when the user keeps separate work and personal accounts.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
whitelabel-ordering
TDQS
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of disclosing behavior. 'Show' implies a read-only operation, and the description states what information is surfaced (signed-in accounts, active account, per restaurant). It does not explicitly confirm absence of side effects or mention any authentication assumptions, but for a simple list operation this is reasonably transparent.
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 concise sentences with no filler. The main action and scope are front-loaded, followed by a briefly stated practical use case. Every sentence earns its place.
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 zero-parameter list tool, the description fully conveys the tool's purpose and likely output. It doesn't detail the exact return format, but no output schema exists and the description sufficiently explains what the agent can expect. The sibling context makes the tool's role even clearer.
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?
The tool has zero parameters and the schema is empty, so the baseline is 4. The description adds context about what the output covers, which is helpful, and no parameter documentation is needed.
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?
The description uses a specific verb ('Show') and resource ('which accounts are signed in, per restaurant, and which one is active'), clearly distinguishing it from sibling tools like login, logout, and switch_account that perform actions rather than list state.
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?
It gives a clear usage context: 'Useful when the user keeps separate work and personal accounts.' It does not explicitly say when not to use it or name alternative tools, but the context is enough for an agent to know when this listing tool fits.
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.
TDQS
A4.4/5.0
Disambiguation5/5
Each tool targets a distinct action and resource: order status vs. order staging vs. order placement, vendor discovery vs. menu retrieval, and login initiation vs. code submission. There is no overlap or ambiguity; even sequential tools like prepare_order and place_order are clearly separated by their purpose.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., check_order, list_vendors, prepare_order). Even the login and logout tools fit the pattern as single verbs, and there is no mixing of conventions.
Tool Count5/5
With 10 tools, the surface is well-scoped for a restaurant ordering domain. It covers discovery, menu browsing, account management, login flow, order staging, placement, and status checking without feeling bloated or too thin.
Completeness4/5
The core ordering lifecycle is covered end-to-end (vendor -> menu -> login -> prepare -> place -> check). The only noticeable gaps are the absence of an explicit address-saving tool (though referenced in the login description) and no order cancellation or update capability, though these may be out of scope for typical ordering workflows.