Skip to main content
Glama
Restroworks Restaurant POS MCP server

Restroworks Restaurant POS MCP server

restroworks_restaurant_pos_open

Open a Restroworks Restaurant POS page in your signed-in Cloud Browser to review outlet sales, orders, inventory, and menus.

Instructions

Open a Restroworks Restaurant POS page in your signed-in Cloud Browser (default https://restroworks.biz) to work with review outlet sales, orders, inventory and menus.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://restroworks.biz

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose that the page opens in a signed-in Cloud Browser, which is useful auth/session context. It does not describe whether it opens a new tab or navigates the current page, what happens if the page is already open, or how failures are surfaced.

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?

The description is a single front-loaded sentence with no obvious filler. The phrase 'review outlet sales' is slightly ambiguous, but overall it is efficient and easy to scan.

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

Completeness3/5

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

For a low-complexity browser-open tool with one optional parameter, the description covers the core action and default URL. It still leaves relevant behavioral gaps around navigation semantics, page-load behavior, and response/error expectations, which matter more because no annotations or output schema are present.

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?

The schema already documents the single optional url parameter at 100% coverage, including its default. The description repeats the default URL but adds little parameter-level meaning beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific verb and resource: opening a Restroworks Restaurant POS page in the signed-in Cloud Browser. It also names the business areas available after opening, making the purpose clear. It does not explicitly differentiate itself from sibling tools such as click, read, or status, but the distinction is reasonably obvious.

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?

The phrase 'to work with review outlet sales, orders, inventory and menus' gives implied usage context for why an agent would open the page. However, it does not say when to use this tool versus alternatives like read, status, or click, nor does it state prerequisites beyond the signed-in browser.

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