CDF Finance

Perfil do usuário

get_profile

Read-only

Retorna o perfil completo do usuário autenticado: dados cadastrais, negócio (CNPJ/website, se hasBusiness), plano e status de assinatura (Stripe), e vínculo com planejador (plannerId). Único campo omitido é phone, redigido antes de sair do servidor MCP — mesmo que fosse pedido explicitamente, não é devolvido.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`cep`	No
`name`	No
`plan`	No
`slug`	No
`type`	No
`email`	No
`auth0Id`	No
`picture`	No
`currency`	No
`location`	No
`createdAt`	No
`plannerId`	No
`updatedAt`	No
`coverImage`	No
`occupation`	No
`hasBusiness`	No
`businessCnpj`	No
`businessName`	No
`menuPreference`	No
`businessWebsite`	No
`stripeCustomerId`	No
`subscriptionStatus`	No
`onboardingCompleted`	No
`stripeSubscriptionId`	No
`subscriptionCurrentPeriodEnd`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already signal read-only and non-destructive behavior, and the description adds a valuable behavioral detail: the phone field is redacted server-side and will never be returned even if requested. This goes beyond the structured metadata and prevents the agent from expecting data that will never exist.

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?

A single dense sentence delivers the resource, the full field list, and the key redaction caveat with no filler. Information is front-loaded and the caveat is logically appended without bloating the description.

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?

For a no-parameter read-only tool with an output schema available, the description is complete: it identifies the target user, lists the returned data, and states the one notable omission. Nothing else is needed for an agent to call it correctly.

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 the input schema coverage is 100%, so there is no parameter documentation burden on the description. The description appropriately focuses on the return payload instead of inventing parameter guidance.

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 verb ('Retorna') and a well-defined resource: the complete profile of the authenticated user, enumerating the exact data groups returned (registro, negócio, plano/assinatura, plannerId). This makes it unmistakably distinct from the sibling update_profile and other read-only tools.

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 makes clear this is the tool for fetching the authenticated user's full profile, and the read-only naming reinforces when it applies. It does not explicitly name alternatives or exclusion cases, but for a zero-parameter getter the intended context is clear.

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

All CDF Finance tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation3/5

The tools are individually well-described and many cross-reference their closest neighbors, but the set contains several easily confused clusters: create_transaction/confirm_new_transaction, update_equity/add_equity_valuation, the invoice tools (current_invoice, next_invoice, list_pending_invoices, get_invoice), and the many analytics/projection tools. The descriptions help a careful reader, but with 81 tools an agent is likely to misselect among these overlapping surfaces.

Naming Consistency3/5

CRUD operations consistently use create_/list_/update_/delete_ plus a resource noun, and all names are snake_case. However, there is a large second group of noun-phrase analytics tools (cashflow_forecast, spending_projection, categories_insights, transport_routine) plus one-off verbs such as can_afford, pay_invoice, and validate_current_invoices, so the naming convention is mixed even though it remains readable.

Tool Count1/5

81 tools is far beyond the practical MCP tool surface and exceeds the rubric's 50+ extreme-mismatch threshold. Even if each tool maps to a real finance endpoint, the volume overwhelms an agent's context window and makes selection much harder.

Completeness4/5

The server covers the finance lifecycle extensively: accounts, cards, invoices, transactions, recurring rules, budgets, goals, debts, equities, categories, tags, cost centers, profile, projections, and insights all have working read/write paths. Minor gaps remain, such as no update/delete for tags and no direct update/delete for system-generated invoices, but agents can usually work around these.

Perfil do usuário

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources