Skip to main content
Glama
Sign In
finance-mcp-server

finance-mcp-server

by Marcusdt-UX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Data Overview

finance_data_overview
Read-onlyIdempotent

Retrieve a summary of all financial data: total transactions, date range, last import, and category-wise inflow/outflow totals. Use this to understand available data before analysis.

Instructions

Summarize what's in the store: total transaction count, date span, last import time, and per-category inflow/outflow totals across all history. Call this first to know what data is available. No args.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds value by detailing the exact summary content (transaction count, date span, last import time, per-category totals), going beyond what annotations provide. No contradictions.

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?

Two sentences: first describes the output, second gives usage guidance and notes no arguments. No extraneous words, front-loaded with purpose. Every word earns its place.

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 zero parameters, full annotations, and a clear description of return content, the description is complete. It lacks an explicit output schema but sufficiently explains what the tool returns. Sibling tools are diverse, but the overview tool's purpose is well-covered.

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

Parameters4/5

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

The input schema has zero parameters, so schema coverage is effectively 100%. With no parameters, the description has no need to add parameter details, and the baseline score of 4 is appropriate.

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?

The description clearly states the tool summarizes store data including transaction count, date span, last import time, and per-category inflows/outflows. It uses the verb 'summarize' and specifies the resource, distinguishing it from sibling tools like finance_search_transactions or finance_spending_by_category.

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?

Explicitly says 'Call this first to know what data is available', providing clear guidance on when to use it. However, it does not explicitly mention when not to use it or list alternatives, missing a point for full marks.

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