Skip to main content
Glama
Sign In

CDF Finance

by io.github.VessellTech
OverviewDiscussionsAdmin

Visão geral de investimentos

investments_workspace
Read-only

Visão consolidada de investimentos: lista de equities, holdings com ganho/perda (valor atual vs custo, usando a avaliação mais recente de cada ativo), totais agregados, alocação por tipo (agrupada em categorias como Imóveis/Veículos/Investimentos/Liquidez/Bens Pessoais/Outros), fluxo mensal dos últimos 6 meses (contributions = despesas ligadas a investimento, withdrawals = receitas ligadas a investimento) e as 6 movimentações mais recentes. Um só request para o que list_equities + list_equity_valuations exigiriam montar manualmente — use este para dashboard/resumo, e list_equities/list_equity_valuations quando precisar só dos dados crus de um ativo.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "investments_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
flowsNo
totalsNo
equitiesNo
holdingsNo
allocationNo
recentMovementsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context: it uses the latest valuation per asset, defines contributions and withdrawals, groups allocation into specific categories, and limits movements to the six most recent ones. It is transparent about aggregation semantics, though it does not mention potential staleness or refresh 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 packs a substantial amount of information into two sentences with clear structure: the main purpose, then the content breakdown, then explicit usage guidance. Every clause adds value and there is no filler.

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?

The description covers what the tool returns, how values are calculated, how categories are grouped, and when to choose an alternative. Since an output schema exists, the description does not need to explain return value details further.

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 tool has zero parameters, so the description has no parameter details to add. The schema fully covers the empty parameter set, and the baseline for a zero-parameter tool is appropriately high.

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 states a specific action and resource: a consolidated investment overview with equities, holdings, gains/losses, totals, allocation, monthly flow, and recent movements. It clearly differentiates from siblings by explicitly comparing itself with list_equities and list_equity_valuations.

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?

It explicitly says to use this tool for dashboards/summaries and to use list_equities/list_equity_valuations when only raw asset data is needed. This gives an agent a clear decision rule and names the alternatives.

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

All CDF 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