Skip to main content
Glama
Sign In
Pocketsmith MCP Server

Pocketsmith MCP Server

by dannyshaw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pocketsmith_get_budget_summary

Retrieve a budget summary for a specified date range and period. Get insights into spending and savings by defining periods like weeks, months, or years with custom intervals.

Instructions

Get budget summary for a period and date range

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "pocketsmith_get_budget_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoThe period for the budget summary (default: months)
intervalNoThe interval for the period (default: 1)
start_dateYesStart date for the budget summary (YYYY-MM-DD)
end_dateYesEnd date for the budget summary (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral transparency. It does not disclose whether the operation is read-only, any authentication requirements, error conditions, or the nature of the response.

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 a single concise sentence that is front-loaded with the key action and resource. Every word serves a purpose, though it could benefit from more structure (e.g., bullet points).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool lacks an output schema and annotations, and the description does not explain what the summary contains, how it is aggregated, or any pagination. Given sibling tools, the description is insufficient for an agent to understand the full context.

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?

The input schema has 100% description coverage for all four parameters, including enums and date format hints. The description adds no additional semantic value beyond what the schema already provides.

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 the tool retrieves a budget summary for a period and date range, using a specific verb and resource. However, it does not differentiate from sibling tools like pocketsmith_list_budget, which may serve a similar function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as pocketsmith_list_budget or pocketsmith_get_trend_analysis. There is no mention of prerequisites or exclusions.

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

Deploy Server

Other Tools