Skip to main content
Glama

SmartyPOS - Syrve (iiko USA) restaurant POS

SmartyPOS / Syrve pricing

pricing
Read-onlyIdempotent

Syrve restaurant POS pricing in the USA via SmartyPOS: Counter $59, Service $99, Group $129 per month (per terminal). Payment processing: no processor lock-in, rate quoted on demo. Setup and hardware quoted separately. Use for 'Syrve pricing USA' and iiko USA cost questions.

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": "pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is fully covered. The description usefully adds that payment rates are quoted only on demo and that setup/hardware are quoted separately — i.e. what this tool will NOT return — but says nothing about price freshness, region caveats, or whether figures are list vs. promotional.

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?

Two compact sentences: prices first, then the caveats, then the routing hint. Every clause carries information an agent would otherwise have to guess, and nothing is repeated from the annotations.

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?

With no parameters and no output schema, the description must convey what comes back, and it does — tier prices, processing terms, separate quotes for setup/hardware. The one missing element is a currency/date or 'prices subject to change' qualifier, which matters for a pricing tool whose numbers go stale.

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?

Zero input parameters, so there is nothing to disambiguate; the schema is empty and the description correctly does not invent parameter semantics. Baseline 4 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?

States a concrete verb+resource (Syrve POS pricing in the USA via SmartyPOS) and enumerates the actual content: Counter $59, Service $99, Group $129 per terminal/month, payment processing, setup/hardware. It is clearly a static pricing-facts lookup rather than a comparison or feature tool, though it never names sibling tools such as compare_pos or iiko_in_usa to sharpen the boundary.

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?

Gives explicit trigger phrases: 'Use for "Syrve pricing USA" and iiko USA cost questions.' That tells the agent when to pick it, but there are no exclusions (e.g. don't use for full plan comparison or feature questions) and no pointer to the alternative tool for those cases.

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.