Skip to main content
Glama
Sign In

CDF Finance

by io.github.VessellTech
OverviewDiscussionsAdmin

Listar contas

list_accounts
Read-only

Lista as contas bancárias/carteiras do usuário: as que ele é dono (userId) e as contas conjuntas onde ele é membro (via AccountMember). Cada item traz myRole (OWNER/MEMBER na conta), isShared e a lista completa de members com dados básicos de cada usuário. Ordenado por criação, mais recente primeiro.

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": "list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the operation as read-only and non-destructive. The description adds valuable behavioral context beyond that: each item contains myRole, isShared, and the complete members list, and results are ordered by creation date descending. This gives the agent a clear expectation of the response shape and ordering.

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?

Three concise sentences front-load the tool's purpose and then add only high-value details: ownership vs membership, per-item fields, and ordering. There is no redundant or filler content.

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 an output schema present and read-only annotations, the description fully covers what an agent needs to understand the tool's behavior: the resource scope, shared-account handling, returned fields, and sort order. Nothing critical is missing for correct invocation.

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 and schema coverage is 100%, so parameter documentation is not a burden. The description still adds relevant context about the implicit user scope and the role/membership model, which is useful even though no parameters exist.

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 uses a specific verb ('Lista') and resource ('contas bancárias/carteiras'), and precisely distinguishes the scope: owned accounts and shared accounts where the user is a member. This makes it clearly distinct from sibling tools like list_cards or list_budgets.

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 clearly establishes what the tool returns and the exact scope of accounts included, so an agent can infer when to call it. It does not explicitly name alternatives or exclusion conditions, but for a simple list tool the context is clear enough.

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