Skip to main content
Glama
BradMorphsters

tuskledger-mcp

get_investments_summary

Retrieve a summary of your investment portfolio including total value, asset allocation among stocks/bonds/cash, top five holdings, and year-to-date percentage gain.

Instructions

Roll-up of investment portfolio: total value, asset allocation (stocks/bonds/cash), top 5 holdings, % YTD gain. The 'how are my investments doing?' answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Dispatch branch for get_investments_summary — calls client.investments_summary()
    if name == "get_investments_summary":
        return client.investments_summary()
  • Tool registration: defines name, description, and input schema (no arguments needed)
    Tool(
        name="get_investments_summary",
        description=(
            "Roll-up of investment portfolio: total value, asset allocation "
            "(stocks/bonds/cash), top 5 holdings, % YTD gain. The 'how are "
            "my investments doing?' answer."
        ),
        inputSchema={"type": "object", "properties": {}, "additionalProperties": False},
    ),
  • HTTP client method that sends GET request to /api/investments/summary and returns the JSON response dict
    def investments_summary(self) -> dict:
        return self._request("GET", "/api/investments/summary")
  • Tool is registered in the TOOLS list on the MCP server
    Tool(
        name="get_investments_summary",
        description=(
            "Roll-up of investment portfolio: total value, asset allocation "
            "(stocks/bonds/cash), top 5 holdings, % YTD gain. The 'how are "
            "my investments doing?' answer."
        ),
        inputSchema={"type": "object", "properties": {}, "additionalProperties": False},
    ),
Behavior4/5

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

With no annotations, the description carries the burden. It discloses the tool produces a summary roll-up (read-only behavior) and lists specific output fields. No contradictions; it is transparent for a simple, read-only tool with no parameters.

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 two sentences, front-loaded with key information, and no redundant words. Every sentence serves a purpose.

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?

Given no parameters and no output schema, the description fully explains the output: total value, asset allocation, top 5 holdings, and YTD gain. An agent can confidently determine when to call this tool.

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?

There are no parameters (schema coverage 100%), so baseline is 4. The description adds value by explaining what the tool returns, which is sufficient for the agent to understand usage.

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's purpose: a roll-up of investment portfolio including total value, asset allocation, top 5 holdings, and YTD gain. It also provides a usage hint ('the how are my investments doing? answer'), making it unambiguous and distinct from siblings like get_holdings or get_net_worth.

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?

The description implies when to use this tool (for an overall portfolio snapshot), but does not explicitly mention when not to use or suggest alternatives. The context is clear but lacks explicit exclusion criteria.

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/BradMorphsters/tuskledger-mcp'

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