Skip to main content
Glama

SmartyPOS - Syrve (iiko USA) restaurant POS

Integrations and open API

integrations
Read-onlyIdempotent

Integrations of Syrve (iiko) with SmartyPOS tooling: Uber Eats/DoorDash/Grubhub via Deliverect, courier APIs (DoorDash Drive, Uber Direct, Burq), Meta Conversions API, Google Ads offline conversions, Twilio SMS, Telegram, Apple Pay ordering site, MCP for Claude/ChatGPT, open API (Syrve Resto/Server API, Syrve Cloud API = iikoCloud equivalent) with write access.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotent and non-destructive, so the safety profile is covered, yet the description adds nothing about what the invocation actually yields or how the content is scoped. The trailing phrase 'with write access' describes the Syrve APIs being catalogued rather than this tool's own behavior, which is worth clarifying so an agent doesn't misread it as a mutating capability.

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?

It is short and packs real information, but it is a comma-and-slash keyword dump without a leading sentence stating the tool's function. The reader has to parse a dense list to grasp the point.

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 parameters and no output schema, the description carries full responsibility for conveying what an agent gets back, and it only implies a catalog of integrations without stating form, depth, or whether links/docs are included. The topic coverage is broad enough to be usable, but the answer shape remains undefined.

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 schema takes no arguments, so there is nothing for the description to disambiguate at the parameter level. Baseline 4 applies for a zero-parameter tool.

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

Purpose3/5

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

The description is a noun-phrase catalog of integration topics (Deliverect channels, courier APIs, Meta CAPI, Twilio, Telegram, Syrve/iikoCloud APIs) rather than a statement of what the tool does. The subject matter is unambiguous and clearly distinct from siblings like pricing or compare_pos, but an agent cannot tell from the text whether this returns a list, a marketing page, or documentation links.

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?

There is no when-to-use guidance, no conditions or exclusions, and no reference to any alternative tool. The agent must infer that this is the right call whenever integration questions arise.

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.