Skip to main content
Glama
BradMorphsters

tuskledger-mcp

get_top_merchants

Identify top merchants by total spending in a date range. Returns merchant name, total amount, transaction count, and monthly trend sparkline.

Instructions

Top N merchants by total spend in a date range. Returns merchant name, total amount, transaction count, and a sparkline of the monthly trend. Useful for 'who am I paying the most?'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateNoISO date.
end_dateNoISO date.
limitNoHow many merchants to return (default 10).

Implementation Reference

  • Dispatch handler for get_top_merchants tool — sets default limit=10 and calls client.top_merchants().
    if name == "get_top_merchants":
        params = {k: v for k, v in a.items() if v not in (None, "")}
        params.setdefault("limit", 10)
        return client.top_merchants(**params)
  • Tool registration/schema definition for get_top_merchants with inputSchema: start_date (string), end_date (string), limit (integer, default 10).
    Tool(
        name="get_top_merchants",
        description=(
            "Top N merchants by total spend in a date range. Returns merchant "
            "name, total amount, transaction count, and a sparkline of the "
            "monthly trend. Useful for 'who am I paying the most?'."
        ),
        inputSchema={
            "type": "object",
            "properties": {
                "start_date": {"type": "string",  "description": "ISO date."},
                "end_date":   {"type": "string",  "description": "ISO date."},
                "limit":      {"type": "integer", "description": "How many merchants to return (default 10)."},
            },
            "additionalProperties": False,
        },
  • HTTP client method top_merchants — issues GET request to /api/analytics/top-merchants with provided filters.
    def top_merchants(self, **filters) -> Any:
        return self._request("GET", "/api/analytics/top-merchants", params=filters)
Behavior2/5

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

No annotations provided. Description only lists return fields; does not disclose read-only nature, authentication requirements, rate limits, or behavior on empty results. Lacks behavioral context beyond output.

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 sentences: purpose, output details, and a use case. No redundancy; front-loaded with actionable information.

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?

Given low complexity and no output schema, description sufficiently covers return values. However, missing details such as sorting order (descending by spend?) and timezone handling could improve completeness.

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%, so description adds little beyond schema. Baseline 3; description's 'date range' and 'top N' mirror schema descriptions without enriching meaning.

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?

Description clearly states the tool returns top merchants by total spend in a date range, listing returned fields. It distinguishes itself from sibling tools like get_spending_summary by focusing on merchants.

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 a use case ('who am I paying the most?') but lacks explicit guidance on when not to use or alternatives. No mention of sibling tools or conditions like data availability.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BradMorphsters/tuskledger-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server