Skip to main content
Glama

My sales

my_sales
Read-onlyIdempotent

Your Sales Report for a period: each sale with its price, cost basis and gain in cents. Requires SlabLineage Pro.

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

Input Schema

NameRequiredDescriptionDefault
periodNo24H, 7D, MTH or YTD (default 7D).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower, and the description still adds real value by disclosing the per-sale payload (price, cost basis, gain in cents) and the Pro entitlement requirement, which is not captured in any structured field. It does not mention pagination or ordering, which is a minor residual gap.

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 short sentences with the payload described first and the prerequisite last, both earning their place. The opening "Your Sales Report" mildly restates the tool name/title, a small redundancy rather than a real cost.

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?

With one optional parameter, full schema coverage, and no output schema, the description carries the needed burden by explaining the returned fields and the subscription prerequisite. Only secondary details (ordering, pagination, what period boundaries mean) are missing for what is otherwise a simple read tool.

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 description coverage is 100% and the single period parameter carries its enum values and default (7D) in the schema. The description only echoes "for a period" without adding format, timezone, or boundary semantics, so the baseline of 3 applies.

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?

The description names a specific resource (sales report for a period) and enumerates the per-sale fields returned (price, cost basis, gain in cents), so an agent knows exactly what the tool produces. It stops short of explicitly contrasting itself with siblings such as log_sale or collection_movers, so differentiation is left to inference.

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 by "Your Sales Report for a period" and the prerequisite "Requires SlabLineage Pro" gives a useful gating condition. However, the description never states when to choose this over related tools (e.g., log_sale for recording sales) or what happens on a free-tier account, leaving routing to the agent.

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