WhatsMyBudgetMCP

analytics_period_uncategorized

Read-only

Find uncategorized transactions for a specific statement period to identify missing category assignments.

Instructions

Get uncategorized transactions for a statement period. Before calling: Call analytics_periods_list first to confirm the requested period exists. If missing, ask the user to choose from available periods. When to use: Use to find uncategorized transactions inside one statement period. Trigger words: uncategorized, missing category, unclassified

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": {
      "period": "<period>"
    },
    "name": "analytics_period_uncategorized"
  }
}

Input Schema

Name	Required	Description	Default
`period`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint. Description adds no new behavioral traits beyond purpose; it does not contradict annotations. Adequate but not extra.

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 sentences plus trigger words, front-loaded with main purpose, then prerequisite, then usage context. No redundant information.

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?

Covers prerequisite and usage context but fails to describe the output (e.g., returns a list of transactions). Given no output schema, this is a notable omission.

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?

Description does not clarify the format of the required 'period' parameter (e.g., 'YYYY-MM' or ID). With 0% schema coverage, this is a significant gap for correct invocation.

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?

Clearly states 'Get uncategorized transactions for a statement period' with a specific verb, resource, and scope. Distinguishes from siblings like analytics_range_uncategorized by specifying 'statement period' and provides trigger words.

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?

Provides explicit prerequisite: call analytics_periods_list first. Includes trigger words for when to use. Lacks explicit exclusion of alternatives but context implies use for single period only.

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