Candor Finance

Refresh Candor connections

candor_connections

Destructive

Refreshes data from financial accounts the user has already connected to Candor. Use when balances or transactions are older than the question needs. Connecting, reconnecting, or disconnecting an institution happens only in the Candor web app. Connected account details are in the accounts dataset.

Input Schema

TableJSON Schema

Name	Required	Description
`args`	No	The selected operation's accepted_args, as published in its contract, including declared shorthand such as the open.acknowledge checkpoint. Action context such as parent_action is a top-level field, not an argument. Request-body fields belong in input unless the operation accepts them as shorthand args.
`input`	No	Inline request body matching the operation's published input schema. Fields such as a note's about link belong inside this object.
`reason`	No	Concise user-visible purpose recorded in immutable action history, including for financial reads. It names the task, such as "Check this month's dining budget", and needs no personal details from the conversation. A reason is not approval. Root operations require it except fixed-reason orientation operations; continuations inherit the parent reason only when no reason is supplied. Fixed-reason orientation operations always use their system reason.
`task_key`	No	Optional stable label grouping operations for the same user task. Omit to inherit the parent task key, if any. It does not schedule work or provide idempotency.
`operation`	Yes	Exact operation id from the Candor operation catalog, such as notes.create.
`parent_action`	No	Existing action id in this workspace, typically returned in next_actions, that this continuation follows. A continuation with the parent's reason joins the parent's root action, whether the reason is omitted (it is then inherited) or repeated exactly; a distinct explicit reason is preserved and starts a new root that keeps this parent link. Fixed-reason orientation operations always start a new root. Omit for a new root action.
`idempotency_key`	No	Stable opaque identity for one logical POST. Reuse only with the same method, path, actor, and body for transport retries. A completed receipt replays its original result, including a refusal; changed input with the same key is rejected. After a refused action and access recovery, use a new key for the new attempt. Follow retryable and recovery guidance if the operation is still running or its outcome is unknown. If omitted, MCP derives a key from this request identity; use an explicit key to deduplicate separate tool invocations.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`action`	No
`errors`	Yes
`status`	Yes
`metadata`	No
`warnings`	Yes
`request_id`	Yes
`generated_at`	Yes
`next_actions`	Yes
`user_message`	No
`data_freshness`	No
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026

changedInput schema / properties / parent_action / description

Previous value: -"Existing action id in this workspace, typically returned in next_actions, whose root identity this continuation inherits. An omitted reason inherits the parent reason; an explicit reason is preserved, except for fixed-reason orientation operations. Omit for a new root action."New value: +"Existing action id in this workspace, typically returned in next_actions, that this continuation follows. A continuation with the parent's reason joins the parent's root action, whether the reason is omitted (it is then inherited) or repeated exactly; a distinct explicit reason is preserved and starts a new root that keeps this parent link. Fixed-reason orientation operations always start a new root. Omit for a new root action."

Changed4 schema fields changedSep 24, 2026

changedInput schema / properties / args / description

Previous value: -"Arguments listed in accepted_args by candor_schema for the selected operation, including declared shorthand such as open.acknowledge checkpoint. Put action context such as parent_action at the top level, including when it comes from a returned next action. Request-body fields belong in input unless the operation explicitly accepts them as shorthand args."New value: +"The selected operation's accepted_args, as published in its contract, including declared shorthand such as the open.acknowledge checkpoint. Action context such as parent_action is a top-level field, not an argument. Request-body fields belong in input unless the operation accepts them as shorthand args."

changedInput schema / properties / input / description

Previous value: -"Inline request body matching the operation input schema returned by candor_schema. Put fields such as a note's about link inside this object."New value: +"Inline request body matching the operation's published input schema. Fields such as a note's about link belong inside this object."

changedInput schema / properties / operation / description

Previous value: -"Exact operation id from candor_schema, such as notes.create. Use the tool indicated by its calls.mcp or next_call."New value: +"Exact operation id from the Candor operation catalog, such as notes.create."

changedInput schema / properties / reason / description

Previous value: -"Concise user-visible purpose recorded in immutable action history, including for financial reads. A reason is not approval. Root operations require it except fixed-reason orientation operations; continuations inherit the parent reason only when no reason is supplied. Fixed-reason orientation operations always use their system reason."New value: +"Concise user-visible purpose recorded in immutable action history, including for financial reads. It names the task, such as \"Check this month's dining budget\", and needs no personal details from the conversation. A reason is not approval. Root operations require it except fixed-reason orientation operations; continuations inherit the parent reason only when no reason is supplied. Fixed-reason orientation operations always use their system reason."

Changed6 schema fields changedSep 14, 2026

addedInput schema / properties / idempotency_key / description

Added value: +"Stable opaque identity for one logical POST. Reuse only with the same method, path, actor, and body for transport retries. A completed receipt replays its original result, including a refusal; changed input with the same key is rejected. After a refused action and access recovery, use a new key for the new attempt. Follow retryable and recovery guidance if the operation is still running or its outcome is unknown. If omitted, MCP derives a key from this request identity; use an explicit key to deduplicate separate tool invocations."

addedInput schema / properties / operation / description

Added value: +"Exact operation id from candor_schema, such as notes.create. Use the tool indicated by its calls.mcp or next_call."

addedInput schema / properties / parent_action / description

Added value: +"Existing action id in this workspace, typically returned in next_actions, whose root identity this continuation inherits. An omitted reason inherits the parent reason; an explicit reason is preserved, except for fixed-reason orientation operations. Omit for a new root action."

changedInput schema / properties / reason / description

Previous value: -"Concise user-visible reason recorded in action history."New value: +"Concise user-visible purpose recorded in immutable action history, including for financial reads. A reason is not approval. Root operations require it except fixed-reason orientation operations; continuations inherit the parent reason only when no reason is supplied. Fixed-reason orientation operations always use their system reason."

addedInput schema / properties / task_key / description

Added value: +"Optional stable label grouping operations for the same user task. Omit to inherit the parent task key, if any. It does not schedule work or provide idempotency."

changedInput schema / required

Previous value: -[
-  "reason",
-  "operation"
-]New value: +[
+  "operation"
+]

Changed3 schema fields changedSep 11, 2026

changedInput schema / properties / args / description

Previous value: -"Path and query arguments declared by the selected operation. Do not put request-body fields here."New value: +"Arguments listed in accepted_args by candor_schema for the selected operation, including declared shorthand such as open.acknowledge checkpoint. Put action context such as parent_action at the top level, including when it comes from a returned next action. Request-body fields belong in input unless the operation explicitly accepts them as shorthand args."

addedOutput schema / properties / metadata / properties

Added value: +{
+  "view_url": {
+    "format": "uri",
+    "type": "string"
+  }
+}

removedOutput schema / properties / metadata / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

Changed1 schema field changedAug 27, 2026

addedOutput schema / properties / metadata

Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

Changed2 schema fields changedAug 26, 2026

removedOutput schema / properties / summary

Removed value: -{
-  "minLength": 1,
-  "type": "string"
-}

changedOutput schema / required

Previous value: -[
-  "data",
-  "errors",
-  "generated_at",
-  "next_actions",
-  "request_id",
-  "schema_version",
-  "status",
-  "summary",
-  "warnings"
-]New value: +[
+  "data",
+  "errors",
+  "generated_at",
+  "next_actions",
+  "request_id",
+  "schema_version",
+  "status",
+  "warnings"
+]

Changed2 schema fields changedAug 26, 2026

removedOutput schema / $defs / __schema1

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "number"
-    },
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    },
-    {
-      "items": {
-        "$ref": "#/$defs/__schema1"
-      },
-      "type": "array"
-    },
-    {
-      "additionalProperties": {
-        "$ref": "#/$defs/__schema1"
-      },
-      "propertyNames": {
-        "type": "string"
-      },
-      "type": "object"
-    }
-  ]
-}

removedOutput schema / properties / query_scope

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "population": {
-      "additionalProperties": false,
-      "properties": {
-        "included_count": {
-          "maximum": 9007199254740991,
-          "minimum": 0,
-          "type": "integer"
-        },
-        "total_available_count": {
-          "anyOf": [
-            {
-              "maximum": 9007199254740991,
-              "minimum": 0,
-              "type": "integer"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        }
-      },
-      "required": [
-        "included_count",
-        "total_available_count"
-      ],
-      "type": "object"
-    },
-    "query": {
-      "additionalProperties": false,
-      "properties": {
-        "args": {
-          "additionalProperties": {
-            "$ref": "#/$defs/__schema1"
-          },
-          "propertyNames": {
-            "type": "string"
-          },
-          "type": "object"
-        },
-        "operation": {
-          "minLength": 1,
-          "type": "string"
-        }
-      },
-      "required": [
-        "args",
-        "operation"
-      ],
-      "type": "object"
-    }
-  },
-  "required": [
-    "population",
-    "query"
-  ],
-  "type": "object"
-}

Changed2 schema fields changedAug 26, 2026

addedOutput schema / $defs / __schema1

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    },
+    {
+      "items": {
+        "$ref": "#/$defs/__schema1"
+      },
+      "type": "array"
+    },
+    {
+      "additionalProperties": {
+        "$ref": "#/$defs/__schema1"
+      },
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    }
+  ]
+}

addedOutput schema / properties / query_scope

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "population": {
+      "additionalProperties": false,
+      "properties": {
+        "included_count": {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "total_available_count": {
+          "anyOf": [
+            {
+              "maximum": 9007199254740991,
+              "minimum": 0,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "included_count",
+        "total_available_count"
+      ],
+      "type": "object"
+    },
+    "query": {
+      "additionalProperties": false,
+      "properties": {
+        "args": {
+          "additionalProperties": {
+            "$ref": "#/$defs/__schema1"
+          },
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "operation": {
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "args",
+        "operation"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "population",
+    "query"
+  ],
+  "type": "object"
+}

Changed5 schema fields changedAug 20, 2026

addedInput schema / $defs

Added value: +{
+  "__schema0": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      },
+      {
+        "items": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "type": "array"
+      },
+      {
+        "additionalProperties": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      }
+    ]
+  },
+  "__schema1": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      },
+      {
+        "items": {
+          "$ref": "#/$defs/__schema1"
+        },
+        "type": "array"
+      },
+      {
+        "additionalProperties": {
+          "$ref": "#/$defs/__schema1"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      }
+    ]
+  }
+}

addedInput schema / properties / args / additionalProperties / $ref
```
Added value: +"#/$defs/__schema0"
```
addedInput schema / properties / input / additionalProperties / $ref
```
Added value: +"#/$defs/__schema1"
```

addedOutput schema / $defs

Added value: +{
+  "__schema0": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      },
+      {
+        "items": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "type": "array"
+      },
+      {
+        "additionalProperties": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      }
+    ]
+  }
+}

addedOutput schema / properties / next_actions / items / properties / args / additionalProperties / $ref
```
Added value: +"#/$defs/__schema0"
```

First observedAug 17, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds scope context (connection management is out-of-band, account details live in the accounts dataset), but it never explains the destructive/non-idempotent consequences, sync latency, or that a reason and idempotency key are effectively required for a mutating call.

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 short sentences, front-loaded with the action, then the trigger, then the scope boundary. No filler or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, but the tool is an operation-dispatch shape whose required 'operation' field expects an exact catalog id that the description never supplies. For a mutation with a rich generic schema and destructive annotation, the description leaves the agent to discover the operation id elsewhere.

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 seven parameters are already documented in the schema and the baseline is 3. The description contributes no parameter-level meaning at all, not even which operation id this tool dispatches to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: refreshing data from already-connected financial accounts. It also scopes the tool by excluding connection lifecycle actions (connect/reconnect/disconnect happen in the web app), which separates it from adjacent workflows, though it never contrasts itself with read siblings like candor_get or candor_query.

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?

Gives an explicit trigger condition: 'Use when balances or transactions are older than the question needs.' It also states what the tool cannot do (institution connect/reconnect/disconnect), which is a useful exclusion. It does not name an alternative sibling tool for the read-only case.

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

All Candor Finance tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Refresh Candor connections

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources