Skip to main content
Glama
Restroworks Restaurant POS MCP server

Restroworks Restaurant POS MCP server

restroworks_restaurant_pos_close

Close the Restroworks Restaurant POS browser session after completing work to stop credit consumption.

Instructions

Close the Restroworks Restaurant POS browser session when the work is done, so credits stop running.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the consequence of calling it ('credits stop running'), which is real value beyond structured fields, but it says nothing about whether the call is idempotent, what happens if no session is active, or whether it can fail.

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 sentence with the action front-loaded and the reason attached as a trailing clause. There is 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?

For a zero-parameter teardown tool with no output schema and no annotations, the description covers what it closes and why it matters (ending credit consumption). The only meaningful gap is error/no-active-session behavior, which is minor for this complexity.

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 takes zero parameters, so there is no parameter meaning to convey. Baseline 4 applies; nothing in the description is needed to disambiguate non-existent inputs.

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?

Contains a specific verb plus resource: 'Close the Restroworks Restaurant POS browser session.' That is unambiguous and, by antonym, implicitly distinct from restroworks_restaurant_pos_open. It does not explicitly name a sibling or state the boundary condition, which keeps it at 4 rather than 5.

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?

'when the work is done' provides a concrete trigger condition telling the agent when this is appropriate. It states no exclusions and does not mention how this relates to session status checks or reopening, so there is room for more routing guidance.

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