Skip to main content
Glama

SmartyPOS - Syrve (iiko USA) restaurant POS

Compare Syrve with a competitor POS

compare_pos
Read-onlyIdempotent

Neutral, sourced comparison of Syrve/iiko USA (SmartyPOS) vs a competitor restaurant POS. competitor: toast | clover | square | spoton | lightspeed | touchbistro | skytab. Returns pricing, processing, contract lock-in, hardware, API access (open API read/write vs read-only), AI, source URLs and checked date (2026-11). Use for Toast alternative, Syrve vs Toast, leave Toast contract questions.

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": {
      "competitor": "<competitor>"
    },
    "name": "compare_pos"
  }
}

Input Schema

NameRequiredDescriptionDefault
competitorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing the payload of the response (pricing, processing, contract lock-in, hardware, API access mode, AI) plus source URLs and a checked date, which tells the agent the answer is citable and time-stamped.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is front-loaded and information-dense, and the return-field list earns its place. But the closing 'Use for Toast alternative, Syrve vs Toast, leave Toast contract questions' reads as keyword stuffing with a garbled final clause, weakening an otherwise tight definition.

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 one-parameter, read-only tool with no output schema this is largely sufficient: valid inputs and expected return content are both covered. Missing are the behavior on an unsupported competitor and any note on scope limits of the 'neutral' comparison, which an agent would need to answer follow-ups confidently.

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?

Schema coverage is 0% and the single 'competitor' property is a bare string, so the description carries the burden — and it does, by listing the accepted values (toast | clover | square | spoton | lightspeed | touchbistro | skytab). It stops short of saying what happens for an unlisted competitor or whether the value is case-sensitive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Neutral, sourced comparison of Syrve/iiko USA (SmartyPOS) vs a competitor restaurant POS') and enumerates the compared dimensions, so an agent can distinguish it from siblings like pricing or syrve_features without opening the schema.

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?

Offers trigger phrasings ('Toast alternative', 'Syrve vs Toast'), which implies when to route here. However the trailing clause 'leave Toast contract questions' is grammatically broken and does not clearly state an exclusion, and no sibling alternative (e.g. pricing, integrations) is named for related-but-different intents.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.