Skip to main content
Glama
Restroworks Restaurant POS MCP server

Restroworks Restaurant POS MCP server

restroworks_restaurant_pos_read

Reads the current restaurant POS page, returning its text plus numbered buttons, links, and fields so an AI agent can inspect the screen and target elements.

Instructions

Read the current Restroworks Restaurant POS page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full behavioral burden. It conveys that this is a non-mutating inspection of the page and lists the categories of content returned, which is useful, but it omits what happens when no POS page is open, whether the element numbering is stable across calls, and whether the read is scoped to a viewport or the entire page.

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?

A single action-first sentence with the resource stated up front and the returned content types immediately after. No filler, no repetition of the tool name, and nothing that could be trimmed without losing information.

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 simple one-optional-parameter read tool with no output schema, the description usefully enumerates the shape of the return (text, numbered buttons, links, fields), which compensates for the missing output schema. The remaining gap is the precondition of an open page and the semantics of the numbering, which keeps it below a 5.

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 single optional parameter is documented in-schema as 'Read only inside this element.' The description does not reference the element parameter or explain whether the integer refers to the same numbers surfaced in the 'numbered buttons' output, so it adds no meaning beyond the schema. Baseline 3 applies.

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 uses a specific verb ('Read') and a specific resource ('the current Restroworks Restaurant POS page'), then enumerates what is captured: text, numbered buttons, links and fields. That distinguishes it well from the action siblings (click, type, open, close), though it never explicitly says 'use this before/after X', so the differentiation is inferred from what it returns rather than stated.

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: 'current' signals an already-open page must exist, and 'numbered buttons' hints the numbering feeds the click tool. There is no explicit when-to-use, no statement of what to do if no page is open, and no named alternative for interacting versus inspecting.

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