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_compound_interest, calculate_debt_to_income, calculate_emergency_fund, calculate_opportunity_cost, calculate_refi_breakeven, calculate_runway, compare_debt_consolidation, compare_mortgage_terms, compare_payoff_strategies, compare_payoff_vs_invest, compare_rent_vs_buy, optimize_401k_match, 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. "compare_rent_vs_buy") or "shared". Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional: filter entries by category, the canonical MCP tool name (e.g. \"rent_vs_buy\") or \"shared\". Case-insensitive."New value: +"Optional: filter entries by category, the canonical MCP tool name (e.g. \"compare_rent_vs_buy\") or \"shared\". Case-insensitive."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint true, idempotentHint true, and destructiveHint false, so the description does not need to restate safety. It adds substantial behavioral detail: the 'calculation, not advice' disclaimer, the always-inline-JSON return, index vs verbose modes, ~20KB size, and validation_error behavior for unrecognized categories. 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 well-structured with a disclaimer, purpose, usage note, and parameter details, and the key facts are front-loaded. It is somewhat lengthy due to the full category list, but each sentence earns its place. It could be slightly more concise, but it remains clear and organized.

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

Completeness5/5

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

With no output schema, the description fully carries the burden of explaining return formats: index mode returns only category+name (~20KB), verbose mode returns all 10 citation fields, and single-entry mode includes all fields. It also covers validation_error behavior and how this tool fits among the calculation siblings. Nothing an agent needs to call it correctly is missing.

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

Parameters5/5

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

Though schema coverage is 100%, the description goes beyond the schema by listing all 14 valid category values, explaining that name requires category, and clarifying that verbose is ignored when name is present. It also describes error responses for invalid categories, which is not in the schema. This adds meaningful usage context.

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 returns named default values used by Senaro Finance tools with source citations. It distinguishes itself from calculation siblings by explicitly framing itself as a catalog to consult before other tools, and notes it always returns inline JSON without an 'output' parameter. This is a specific verb+resource with clear scope.

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?

The description explicitly instructs agents to use this tool before calling other tools to understand applicable assumptions. It also clarifies that it does not accept an 'output' parameter and explains parameter interactions (name requires category, verbose ignored when name is present). Default behavior for no arguments is specified as index mode. This leaves no ambiguity about when and how to use it.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources