Skip to main content
Glama

Kartic - Digital Loyalty Stamp Cards For Local Businesses

Get business stats

get_business_stats
Read-only

Use when a signed-in merchant asks for stamp/customer/reward stats. Requires owner or manager. Returns a short analytics snapshot for the last N days (default 30).

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_business_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLookback window in days (default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral facts: an owner/manager permission requirement and that the result is a short snapshot rather than a full export. It does not disclose which metrics are included or any limits beyond the day window, leaving breadth ambiguous.

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 short sentences, front-loaded with the usage trigger, then the permission requirement, then the return shape. No filler or redundant framing.

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 single-parameter, read-only tool with a full annotation set and complete schema, the description covers trigger, authorization, and return shape. With no output schema, a little more on what the snapshot contains would close the last gap.

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% and the single parameter is fully documented, including the default of 30. The description's 'last N days (default 30)' merely restates the schema and omits the 1–365 bounds, so it adds no meaning beyond structured data.

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 (stamp/customer/reward stats) and a clear outcome (analytics snapshot), so the agent knows exactly what data this returns. It does not need to differentiate against siblings, since none of the listed tools report analytics, but it also never explicitly says so.

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?

'Use when a signed-in merchant asks for stamp/customer/reward stats' gives an explicit trigger condition, and 'Requires owner or manager' states the authorization prerequisite. There is no when-not guidance or named alternative for adjacent questions (e.g., setup explanation), though none is obviously required.

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.

Resources