Skip to main content
Glama
Restroworks Restaurant POS MCP server

Restroworks Restaurant POS MCP server

restroworks_restaurant_pos_status

Verify your Cotlet.dev account, credits, and Restroworks Restaurant POS connection before running sales, inventory, or menu actions.

Instructions

Check that your Cotlet.dev account and Restroworks Restaurant POS are ready: account, credits and Restroworks Restaurant POS connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Check" implies a non-mutating read, but the description says nothing about the result format, what happens if the account or POS is not ready, or whether this consumes credits or triggers a live connection attempt — all meaningful for a connectivity diagnostic.

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 front-loaded sentence with the three checked items listed after the colon. Slight redundancy in repeating "Restroworks Restaurant POS" (once as target, once as connection) costs a point but nothing is wasted.

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?

With no annotations and no output schema, the description is the only source of truth. It names the three things verified, which is useful, but never indicates what the response looks like or how to interpret a negative result, leaving the agent guessing about the return value.

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 the 4 baseline applies; there is no parameter meaning for the description to add or omit.

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 ("Check") and enumerates the exact resources being verified: the Cotlet.dev account, credits, and the Restroworks Restaurant POS connection. This clearly separates it from the action-oriented siblings (click, close, open, read, type), which perform operations rather than report readiness. It stops short of a 5 because the name/sibling contrast is only implicit.

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?

Readiness framing implies a pre-flight check before using the sibling action tools, but the description never states when to call this versus alternatives, nor any exclusions. Usage must be inferred from the word "ready" rather than from explicit guidance.

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