Loyal Digicard

Analytics

get_analytics

Read-onlyIdempotent

The same numbers as Owner › Analytics for a period, optionally for one branch and/or one program, plus stamp visits per day. With a branch filter the branch time zone is used (as in the dashboard); otherwise the business time zone.

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

Input Schema

Name	Required	Description	Default
`period`	No		30d
`branch_id`	No	From list_branches
`program_id`	No	From list_programs

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds genuinely non-obvious behavior: which time zone applies when a branch filter is present versus absent, and that the result includes per-day stamp visits. It does not mention result size, aggregation granularity limits, or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with what is returned, then the time-zone caveat that an agent would otherwise get wrong. No filler, though the dashboard reference in the opening clause is slightly indirect phrasing.

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?

For a read-only three-parameter tool with no output schema, the description must explain what comes back, and it largely delegates that to an external UI reference ('the same numbers as Owner › Analytics') that an agent cannot resolve. Time-zone and stamp-visit details are complete, but the returned metric set remains underspecified.

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 67%, and the description adds meaning the schema lacks: that branch and program filters are optional and mutually combinable, and that branch_id carries a time-zone side effect. The period enum values and the 30d default are only in the schema, which is acceptable.

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 resource (analytics numbers matching Owner › Analytics) with scope qualifiers: a period, optional single branch and/or program, plus per-day stamp visits. An agent can tell this is a scoped reporting read. It does not explicitly differentiate itself from sibling get_shop_summary, leaving the closest alternative ambiguous.

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?

Usage is implied: pick a period, optionally narrow to one branch and/or one program. There is no explicit when-to-use vs when-not guidance and no mention of how this differs from get_shop_summary, so the agent must infer the boundary.

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

All Loyal Digicard tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?