Skip to main content
Glama
shahlaukik

Money Manager MCP Server

by shahlaukik

dashboard_get_asset_chart

Retrieve historical chart data for a specific asset to analyze performance trends and track financial growth over time.

Instructions

Retrieves historical chart data for a specific asset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetIdYesAsset ID

Implementation Reference

  • The main handler function that validates the input using DashboardGetAssetChartInputSchema, calls the Money Manager API endpoint '/getEachAssetChartData' with the assetId parameter, and returns an object containing the assetId and chartData array.
    /**
     * Handler for dashboard_get_asset_chart tool
     * Retrieves historical chart data for a specific asset
     */
    export async function handleDashboardGetAssetChart(
      httpClient: HttpClient,
      input: unknown,
    ): Promise<AssetChartResponse> {
      const validated = DashboardGetAssetChartInputSchema.parse(input);
    
      const rawResponse = await httpClient.post<RawAssetChartResponse>(
        "/getEachAssetChartData",
        {
          assetId: validated.assetId,
        },
      );
    
      return {
        assetId: validated.assetId,
        chartData: rawResponse.assetChartData || [],
      };
    }
  • Zod schema defining the input for the tool: an object with a required 'assetId' string field (non-empty). Includes TypeScript type inference.
     * Input schema for dashboard_get_asset_chart tool
     */
    export const DashboardGetAssetChartInputSchema = z.object({
      assetId: AssetIdSchema,
    });
    
    export type DashboardGetAssetChartInput = z.infer<
      typeof DashboardGetAssetChartInputSchema
    >;
  • src/index.ts:422-431 (registration)
    MCP tool registration in the TOOL_DEFINITIONS array, including name, description, and JSON schema for input validation (requires assetId).
      name: "dashboard_get_asset_chart",
      description: "Retrieves historical chart data for a specific asset.",
      inputSchema: {
        type: "object" as const,
        properties: {
          assetId: { type: "string", description: "Asset ID" },
        },
        required: ["assetId"],
      },
    },
  • Maps the tool name 'dashboard_get_asset_chart' to its handler function 'handleDashboardGetAssetChart' in the toolHandlers registry used by executeToolHandler.
    // Dashboard
    dashboard_get_overview: handleDashboardGetOverview,
    dashboard_get_asset_chart: handleDashboardGetAssetChart,
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 of behavioral disclosure. It states 'Retrieves historical chart data,' implying a read-only operation, but doesn't specify permissions, rate limits, data format, time ranges, or what 'historical' entails. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly, with every part contributing essential information.

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 complexity of retrieving historical data and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'historical chart data' includes (e.g., time periods, chart types, data format), which is crucial for an agent to use this tool effectively. The high schema coverage helps with parameters, but overall context is insufficient.

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, with 'assetId' documented as 'Asset ID.' The description adds no additional parameter details beyond implying it's for a 'specific asset,' which aligns with the schema. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't enhance parameter understanding.

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 action ('Retrieves historical chart data') and resource ('for a specific asset'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'dashboard_get_overview' or 'summary_get_period', which might also retrieve dashboard-related data, so it doesn't reach the highest clarity level.

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. With siblings like 'dashboard_get_overview' and 'summary_get_period' that might retrieve related dashboard or summary data, there's no indication of context, prerequisites, or exclusions for this specific chart retrieval tool.

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