Skip to main content
Glama
Sign In
mcploy

mcploy

by ogarciabrena
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List pos_devices

loyverse_list_pos_device

Retrieve POS devices from Loyverse. Supports filtering by store identifier and pagination to list physical or virtual terminals.

Instructions

List pos_devices from Loyverse (GET /pos_devices). Supports cursor pagination. Physical/virtual POS terminals, one per store. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

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

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, Loyverse default 25, max 250.
queryNoExtra query string filters supported by this endpoint (e.g. store_id, updated_at_min, created_at_max).
cursorNoPagination cursor from a previous response.
fetch_allNoIf true, follows pagination automatically and returns every page combined (capped at 20 pages for safety). If false/omitted, returns a single page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Discloses key behaviors: supports cursor pagination, field names follow Loyverse API, error handling for 400s. Since no annotations are present, the description carries the full burden. Could be improved by explicitly stating the tool is read-only and does not modify state.

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?

Three concise, front-loaded sentences covering purpose, pagination, and error behavior. No wasted words; every sentence adds value.

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?

Adequately covers listing, pagination, and error behavior, but lacks description of the output format (e.g., list of device objects) since there is no output schema. Could be more complete by briefly summarizing the response structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents each parameter. The description does not add additional semantics beyond noting pagination. Baseline score of 3 is appropriate.

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?

Clearly states the tool lists POS devices from Loyverse via GET /pos_devices, and describes them as physical/virtual terminals. However, it does not explicitly differentiate itself from the sibling tool 'loyverse_get_pos_device' or other list tools, which would be helpful.

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?

Provides guidance on error handling (400 responses return verbatim error message, adjust fields and retry) but does not specify when to use this tool versus alternatives like loyverse_get_pos_device or other list tools. No 'when to use' or 'when not to use' context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools