Skip to main content
Glama
Sign In
Loyverse MCP Server

Loyverse MCP Server

by imtayyab2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get shift

loyverse_get_shift
Read-only

Fetch a specific shift's data by ID from Loyverse POS to view shift details for reporting and reconciliation.

Instructions

Fetch one shift by id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "shift_id": "<shift_id>"
    },
    "name": "loyverse_get_shift"
  }
}

Input Schema

NameRequiredDescriptionDefault
shift_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already communicate read-only and non-destructive behavior; the description adds the cardinality of returning exactly one shift but no further behavioral context such as error responses or whether missing IDs produce null or an error. This is acceptable for a simple getter but not rich.

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?

The description is a single front-loaded phrase with no filler; every word carries semantic weight.

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 tool with one required parameter and no output schema, the description plus annotations are nearly sufficient: an agent knows to supply shift_id and that the result is a single shift. It lacks explicit mention of alternate list usage or edge cases, but none are essential for basic invocation.

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 0%, and the description only says 'by id' rather than naming shift_id. It adds minimal meaning beyond the schema, though the single parameter's purpose is inferable from its name and the description.

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 states an explicit action ('Fetch'), a specific resource ('shift'), and a retrieval criterion ('by id'), which clearly distinguishes it from list-oriented siblings like loyverse_list_shifts. No ambiguity about what the tool does.

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?

'By id' implies the tool should be used when a single shift identifier is available and a unique shift is wanted, which distinguishes it from loyverse_list_shifts. It does not explicitly name alternatives or exclusion conditions, so it stops short of a 5.

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