WhatsMyBudgetMCP

analytics_range_outliers

Read-only

Identify largest transactions and unusual spending in any custom date range to detect outliers.

Instructions

Get largest transactions in a date range. When to use: Use for largest or unusual transaction questions over a custom date range. Trigger words: outliers, largest transactions, unusual spending, biggest transactions

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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "analytics_range_outliers"
  }
}

Input Schema

Name	Required	Description	Default
`startDate`	Yes
`endDate`	Yes
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations provide readOnlyHint=true and openWorldHint=true, indicating safe read operations. The description adds that the tool returns 'largest transactions,' implying ordering or outlier detection behavior. However, it does not disclose details like data recency, precision, or potential latency. No contradiction with annotations.

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?

The description is short and front-loaded: a clear verb phrase followed by usage guidance. Three sentences are compact, but the trigger words list is slightly redundant with the second sentence. Overall efficient without unnecessary detail.

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 analytics tool with 3 parameters and no output schema, the description covers the core purpose and usage context. However, it omits details about return structure (e.g., list format, fields included, sorting) and any pagination or throttling behavior. Adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% coverage (no parameter descriptions). The description does not explain the meaning of startDate, endDate, or limit beyond what the schema constraints imply (formats, min/max). For example, it doesn't clarify that limit caps the number of results. This leaves the agent relying solely on schema patterns and defaults.

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 clearly states it retrieves 'largest transactions in a date range.' The verb 'Get' and resource 'largest transactions' are specific. While it distinguishes from period-based tools via the range keyword, it does not explicitly differentiate from other range analytics tools among siblings, which are numerous.

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?

The description explicitly says 'Use for largest or unusual transaction questions over a custom date range' and lists trigger words. This provides clear context for when to use, but it lacks guidance on when not to use or mention of alternative tools for similar queries.

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