Skip to main content
Glama

Senaro Personal Finance

by ai.senaro
OverviewDiscussionsAdmin

Default Assumptions Catalog

list_defaults
Read-onlyIdempotent

Calculation, not advice. Verify with a professional before acting.

Returns named default values used by Senaro Finance tools with source citations. Use before calling other tools to understand what assumptions apply automatically. This tool does not accept an 'output' parameter; it always returns inline JSON.

JSON parameters (all optional): category: string. Filter entries by category: the canonical MCP tool name that consumes the default, or "shared" for a default consumed by two or more tools (or not yet wired to a specific tool). Case-insensitive. The 14 valid values: calculate_cc_payoff, calculate_debt_to_income, calculate_emergency_fund, calculate_opportunity_cost, calculate_runway, compare_debt_consolidation, compare_mortgage_terms, compare_strategies, compound_interest, optimize_401k_match, payoff_vs_invest, refi_breakeven, rent_vs_buy, shared. An unrecognized value returns validation_error listing the accepted set. name: string. Return one full entry. Requires category. Returns validation_error if not found. verbose: boolean. Return all 10 citation fields per entry instead of just category+name. Ignored when name is also present (single entry always includes all fields). Omit category to get the full verbose catalog.

Default (no args): index mode. Every entry with just category and name fields (~20 KB).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional: return one full entry. Requires category. Returns validation_error if not found.
verboseNoOptional: return all 10 citation fields per entry instead of just category+name.
categoryNoOptional: filter entries by category, the canonical MCP tool name (e.g. "rent_vs_buy") or "shared". Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive. The description adds genuinely new behavioral context: the tool never accepts an 'output' parameter and always returns inline JSON, the ~20 KB size of default index mode, the validation_error contract for bad categories, and the verbose-ignored-when-name-present rule. Slightly verbose but substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The behavioral/citation framing is front-loaded and useful, but the parameter block is long and partly duplicative of the schema, and enumerating 14 category values inline inflates the description. Every sentence earns its place, but it is not tightly trimmed.

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?

For a 3-param, no-output-schema read-only catalog, the description covers invocation modes, error contracts, and scope thoroughly. It omits an explicit statement of what a 'default' entry actually contains beyond 'citation fields', which is the only notable gap.

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?

Schema coverage is 100% (baseline 3), and the description still adds cross-parameter semantics the schema lacks: name requires category, the 14 canonical enum values, the case-insensitive matching, and the interaction between verbose and name. This exceeds what the flat schema communicates.

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?

States a specific verb and resource: returns named default values used by Senaro Finance tools with source citations. Distinguishes itself from the calculate_/compare_ siblings by being a metadata/catalog tool rather than a calculator, and explicitly positions itself as a pre-step ('Use before calling other tools').

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance: 'Use before calling other tools to understand what assumptions apply automatically.' Also explains the index-vs-detail modes and the no-args default behavior, leaving nothing to inference.

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

All Senaro Personal Finance toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources