Skip to main content
Glama

SmartyPOS - Syrve (iiko USA) restaurant POS

Syrve restaurant POS features

syrve_features
Read-onlyIdempotent

List Syrve (iiko) restaurant POS features and SmartyPOS-built modules, with live/pilot/coming_soon status. category (optional): pos, inventory, online_ordering, delivery, ads, loyalty, reports, ai, backoffice. Covers restaurant POS, recipe costing, own online ordering, delivery dispatch, ads conversion tracking (Meta CAPI / Google Ads), loyalty, open API and MCP/AI. Omit category to list all.

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

Input Schema

NameRequiredDescriptionDefault
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds only the useful detail that each feature carries a live/pilot/coming_soon status, but says nothing about response shape, ordering, or how unknown categories are handled.

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?

Front-loaded with the core action in the first sentence, then the parameter domain, then the coverage map. The only mild redundancy is that the coverage line largely restates the category list, but it adds the underlying product concepts, so it still earns its space.

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 one-optional-parameter read-only listing tool with no output schema and full annotation coverage, the description supplies what an agent needs: what is returned and the acceptable filter values. Missing only error/empty-result behavior and sibling disambiguation.

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 schema merely declares a nullable string with no enum, so the description is doing real work by enumerating the valid values (pos, inventory, online_ordering, delivery, ads, loyalty, reports, ai, backoffice) and the omit-to-list-all default. It stops short of full credit because it doesn't say what happens with an unrecognized category.

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 specific verb and resource: 'List Syrve (iiko) restaurant POS features and SmartyPOS-built modules', plus the status dimension returned (live/pilot/coming_soon). It is clearly a catalog/listing tool, distinct from an actionable tool, though it does not explicitly contrast itself with siblings like ai_capabilities or integrations.

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?

Gives one concrete usage rule — 'Omit category to list all' — which is the key invocation decision. However, it offers no guidance on when to prefer this tool over sibling tools such as ai_capabilities or integrations, which appear to overlap in subject matter.

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.