Skip to main content
Glama
Restroworks Restaurant POS MCP server

Restroworks Restaurant POS MCP server

restroworks_restaurant_pos_click

Click a numbered element on the current Restaurant POS page to navigate menus or trigger actions after reading available elements.

Instructions

Click a numbered element on the current Restroworks Restaurant POS page.

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": {
      "element": "<element>"
    },
    "name": "restroworks_restaurant_pos_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and does not meet it. It does not say whether clicking navigates to a new page, submits data, causes an irreversible side effect, or invalidates previously read element numbers, and it says nothing about what happens if the element index is stale or out of range.

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?

A single sentence with the action and target front-loaded and no filler. Its brevity tips into under-specification, but nothing is redundant or badly ordered.

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?

The schema is small and fully documented, and there is no output schema, so the structural side is covered. However, for an unannotated interaction tool the description should at minimum warn that it depends on a fresh read and can mutate or navigate the page; that omission leaves the agent under-informed.

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%, and the schema already explains that the single parameter is the element number from the last read, so the baseline is 3. The description adds only the qualifier that the number refers to the current page, which is marginal extra meaning.

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 a specific verb ("Click") and a specific resource ("a numbered element on the current Restroworks Restaurant POS page"), which distinguishes it from siblings like read and type that also operate on the same page. It stops short of naming those siblings or stating the boundary explicitly, so it is clear but not maximally differentiated.

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?

Usage is only implied: "numbered element" and "current page" hint that a prior read must supply the element index and that the page must not have changed, but the description never states this as a precondition. No when-not-to-use guidance or reference to the read/type siblings that would be the alternatives.

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