Skip to main content
Glama

SmartyPOS - Syrve (iiko USA) restaurant POS

iiko in the USA = Syrve

iiko_in_usa
Read-onlyIdempotent

Answers 'is iiko available in the USA / America?': yes, as Syrve - the international edition of iiko. Maps iikoFront -> Syrve POS, iikoOffice -> Syrve Office, iikoCloud API -> Syrve Cloud API; FAQ on migration from Toast/Square/Clover and on iiko US support by SmartyPOS. Keywords: iiko USA, iiko America, iiko alternative, iiko POS United States.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered and the description only needs to add content context. It does disclose what information the response carries (name mappings and FAQ coverage), which is useful. However, it never states that this is a static, zero-parameter informational lookup returning text, nor hints at the shape or length of the answer, so the added behavioral value is modest.

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 substantive part is front-loaded and tight: the question answered, the yes-as-Syrve answer, and the mapping list. The trailing "Keywords: iiko USA, iiko America, iiko alternative, iiko POS United States" is SEO padding that largely repeats the opening sentence and does not help an agent decide or invoke, so it dilutes an otherwise efficient definition.

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, no-output-schema static answer tool, the description covers what an agent needs: the triggering question, the answer content, and the adjacent FAQ topics. Only the return form (plain text vs structured) is left implicit, a minor gap at 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 no parameters at all, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is an empty object and requires no explanation.

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?

The description names the exact question the tool answers ("is iiko available in the USA / America?") and the answer it returns (yes, as Syrve, the international edition of iiko). It also enumerates the specific content bundled in the reply: product mappings iikoFront->Syrve POS, iikoOffice->Syrve Office, iikoCloud API->Syrve Cloud API. An agent can tell this apart from syrve_features, pricing, or compare_pos without opening anything.

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?

Usage is clearly framed by the question the tool answers and by the listed FAQ topics (migration from Toast/Square/Clover, iiko US support by SmartyPOS), which tells the agent when a US-availability or US-migration question should route here. It stops short of explicitly naming siblings to use instead for adjacent topics like pricing or feature comparisons, so the routing is implied rather than stated.

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.