CDF Finance

Criar cartão

create_card

Cria um novo cartão de crédito para o usuário autenticado, com limite usado e fatura atual zerados.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "closingDay": "<closingDay>",
      "dueDay": "<dueDay>"
    },
    "name": "create_card"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Nome/apelido do cartão, ex: 'Nubank Roxinho'
`brand`	No	Ex: VISA, MASTERCARD
`color`	No	Cor hex para exibição, ex: #3B82F6
`limit`	No	Limite total do cartão. Omita para criar um cartão 'Sem Limite' (sem teto de crédito)
`dueDay`	Yes	Dia do vencimento da fatura (1-31)
`currency`	No	Moeda ISO 4217, default BRL
`accountId`	No	ID da conta usada para pagar a fatura deste cartão
`closingDay`	Yes	Dia do fechamento da fatura (1-31)
`lastFourDigits`	No	Últimos 4 dígitos do cartão, só para exibição

Output Schema

Name	Required	Description
`id`	No
`name`	No
`brand`	No
`color`	No
`limit`	No	Limite do cartão; null = Sem Limite
`dueDay`	No
`userId`	No
`currency`	No
`accountId`	No
`createdAt`	No
`limitUsed`	No
`updatedAt`	No
`closingDay`	No
`currentInvoice`	No	Total da fatura atual (não paga)
`lastFourDigits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 1, 2026

changedInput schema / properties / accountId / description

Previous value: -"Conta associada ao pagamento da fatura"New value: +"ID da conta usada para pagar a fatura deste cartão"

addedInput schema / properties / color

Added value: +{
+  "description": "Cor hex para exibição, ex: #3B82F6",
+  "type": "string"
+}

addedInput schema / properties / currency

Added value: +{
+  "description": "Moeda ISO 4217, default BRL",
+  "type": "string"
+}

addedInput schema / properties / lastFourDigits / description

Added value: +"Últimos 4 dígitos do cartão, só para exibição"

changedInput schema / properties / limit / description

Previous value: -"Limite total do cartão"New value: +"Limite total do cartão. Omita para criar um cartão 'Sem Limite' (sem teto de crédito)"

addedInput schema / properties / name / description

Added value: +"Nome/apelido do cartão, ex: 'Nubank Roxinho'"

changedInput schema / required

Previous value: -[
-  "name",
-  "limit",
-  "closingDay",
-  "dueDay"
-]New value: +[
+  "name",
+  "closingDay",
+  "dueDay"
+]

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive operation. The description adds behavioral context beyond the annotations by specifying that a newly created card starts with used limit and current invoice at zero and is scoped to the authenticated user. No contradiction with annotations exists.

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, front-loaded sentence that moves from action to resource to behavioral details without filler. Every clause earns its place: scope, resource type, and the zeroed initial state.

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 create tool with an output schema, exhaustive schema descriptions, and safety annotations, the description covers the essential domain semantics that are not in structured fields. Explicit alternative routing is the only missing element, and that is already accounted for in usage_guidelines.

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?

Schema description coverage is 100%, so the baseline is 3 even without parameter information in the tool description. The description adds no field-level semantics, but the input schema fully documents all nine parameters, including requirements and defaults.

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 ('Cria'), a clear resource ('cartão de crédito'), and adds meaningful scope ('para o usuário autenticado') plus initial state details. This distinguishes it from sibling creation tools such as create_account, create_transaction, and update_card.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for creating a new card for the authenticated user, but it never explicitly states when to choose it over alternatives like update_card/delete_card/list_cards. It provides no exclusions or alternative routing, so guidance is only implicit.

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

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.