Skip to main content
Glama
Restroworks Restaurant POS MCP server

Restroworks Restaurant POS MCP server

restroworks_restaurant_pos_guide

Get step-by-step guidance for using Restroworks Restaurant POS to review outlet sales, orders, inventory, and menus, find key screens, and locate the sign-in link before starting tasks.

Instructions

How to work in Restroworks Restaurant POS (review outlet sales, orders, inventory and menus): its screens and the sign-in link. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "restroworks_restaurant_pos_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Restroworks Restaurant POS, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral load. It discloses the content (screens, sign-in link) and the invocation ordering, which is real value, but says nothing about whether the result is a static reference document, whether sign-in requires separate credentials, or what the response looks like. Adequate for a low-risk informational tool, not rich.

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, front-loaded with the scope and parenthetical content list, closed by the actionable instruction. No filler or redundancy.

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?

A simple one-parameter orientation tool with no output schema and no annotations; the description names its coverage areas and its call ordering, which is nearly everything needed. Only slight gaps around return format and sign-in prerequisites remain.

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?

There is one optional parameter, 'task', with 100% schema description coverage, so the schema already defines it. The description never mentions the parameter or explains how phrasing the task changes what guidance is returned, so it adds nothing beyond the schema.

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?

States the resource (Restroworks Restaurant POS) and what the guide contains: screens, sign-in link, and coverage of outlet sales, orders, inventory and menus. It does not name a sibling explicitly, but 'guide' plus 'sign-in link' clearly distinguishes it from action-verb siblings like open, close, click and read.

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?

'Call this first' gives an explicit ordering rule that no sibling would provide. There are no when-not conditions or named alternatives, but for an orientation tool the sequencing instruction covers the main decision an agent faces.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.