Skip to main content
Glama
shahlaukik

Money Manager MCP Server

by shahlaukik

dashboard_get_overview

Retrieve a comprehensive dashboard overview showing asset trends and portfolio breakdown to monitor personal finances and track financial performance.

Instructions

Retrieves dashboard overview with asset trends and portfolio breakdown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the core logic: validates input, calls Money Manager API /getDashBoardData, and transforms raw response into DashboardResponse with assetSummary, monthlyTrend, assetRatio, and debtRatio.
     * Handler for dashboard_get_overview tool
     * Retrieves dashboard overview with asset trends and portfolio breakdown
     */
    export async function handleDashboardGetOverview(
      httpClient: HttpClient,
      input: unknown,
    ): Promise<DashboardResponse> {
      DashboardGetOverviewInputSchema.parse(input);
    
      const rawResponse =
        await httpClient.get<RawDashboardResponse>("/getDashBoardData");
    
      return {
        assetSummary: rawResponse.assetSummary,
        monthlyTrend: rawResponse.assetLine || [],
        assetRatio: rawResponse.assetRatio || [],
        debtRatio: rawResponse.debtRatio || [],
      };
    }
  • Zod schema for tool input validation. Defines empty object since the tool takes no parameters.
    export const DashboardGetOverviewInputSchema = z.object({});
    
    export type DashboardGetOverviewInput = z.infer<
      typeof DashboardGetOverviewInputSchema
    >;
  • Maps tool name to handler function in the internal toolHandlers registry used by executeToolHandler.
    dashboard_get_overview: handleDashboardGetOverview,
  • src/index.ts:413-420 (registration)
    Registers the tool in MCP server's TOOL_DEFINITIONS array, defining name, description, and input schema for protocol discovery.
      name: "dashboard_get_overview",
      description:
        "Retrieves dashboard overview with asset trends and portfolio breakdown.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
    },
  • Registers the input schema in the central ToolSchemas registry for validation lookup.
    dashboard_get_overview: DashboardGetOverviewInputSchema,
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves data, implying a read-only operation, but does not disclose behavioral traits such as authentication needs, rate limits, error conditions, or data freshness. This is a significant gap for a tool with zero annotation coverage.

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?

The description is a single, efficient sentence with zero waste. It is front-loaded with the core action and immediately specifies the data included, making it easy for an agent to parse and understand without unnecessary details.

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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain the return format, structure of the overview, or any behavioral context needed for reliable use. For a data retrieval tool with no structured support, more detail on output and constraints is warranted.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the data retrieved. A baseline of 4 is applied as it compensates for the lack of parameters by describing the output scope.

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 verb ('Retrieves') and resource ('dashboard overview'), specifying what data is included ('asset trends and portfolio breakdown'). It distinguishes from siblings like 'dashboard_get_asset_chart' by indicating a broader overview rather than a specific chart, though not explicitly contrasting them.

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?

The description provides no guidance on when to use this tool versus alternatives like 'dashboard_get_asset_chart' or 'summary_get_period'. It mentions the data retrieved but does not specify use cases, prerequisites, or exclusions, leaving the agent to infer usage from context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shahlaukik/money-manager-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server