Skip to main content
Glama

SmartyPOS - Syrve (iiko USA) restaurant POS

About SmartyPOS and Syrve (iiko USA)

about_smartypos
Read-onlyIdempotent

Who SmartyPOS is and what Syrve is. SmartyPOS (Sheno Inc., Sarasota FL) implements and supports Syrve (the international/US edition of iiko) - a restaurant POS with open API, MCP and AI integrations - for US restaurants; a Toast alternative. Keywords: iiko, iiko USA, Syrve, restaurant POS, open API, MCP, AI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 and openWorldHint=false, so the safety profile is fully covered. The description adds content scope (vendor identity, Syrve/iiko relationship, US positioning) but says nothing about response format or size beyond what the annotations imply.

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 useful, but the trailing 'Keywords:' list (iiko, restaurant POS, open API, MCP, AI) is SEO padding rather than agent guidance, and 'a Toast alternative' reads as marketing rather than selection help.

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, read-only informational tool with no output schema, the description gives enough about what content will come back and what the vendor/product are. Only the missing routing relative to sibling tools keeps it from a 5.

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 and the schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies as no parameter semantics are needed.

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?

Specific: it states it returns who SmartyPOS (the vendor) is and what Syrve/iiko is, including the relationship (Sheno Inc. implements/supports Syrve, the US edition of iiko). That is a clear informational resource distinct from siblings like pricing or syrve_features, though it never explicitly says how it differs from those.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is given, and no sibling tool is named as an alternative for things like feature detail, pricing, or contacting sales. An agent must infer from the topic label alone that this is background/context material.

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.