Candor Finance

Refresh Candor connections

candor_connections

Destructive

Refresh already-connected sources through the Candor API. Financial-source connection, reconnection, and disconnection happen only in the secure Candor web portal; query the accounts dataset to inspect connected financial accounts.

Input Schema

TableJSON Schema

Name	Required	Description
`args`	No	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.
`input`	No	Inline request body matching the operation input schema returned by candor_schema. Put fields such as a note's about link inside this object.
`reason`	No	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.
`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 candor_schema, such as notes.create. Use the tool indicated by its calls.mcp or next_call.
`parent_action`	No	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.
`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.

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

A4/5.0

Behavior3/5

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

The annotations already carry readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the agent knows this is a mutating, non-idempotent operation. The description adds useful context about the portal-only boundary for connection lifecycle. However, it doesn't explain what 'refresh' changes or what destructive behavior might be implied.

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?

Two sentences, both information-dense, with the core purpose front-loaded and the boundary condition in the second sentence. No filler.

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

Completeness4/5

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

For a wrapper tool with 7 generic parameters, an output schema, and annotations covering safety, the description covers the essential selection facts: what it refreshes, what it cannot do, and where to inspect accounts. A small gap is not naming the sibling or explaining the effect of refresh.

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 parameters are documented elsewhere. The description adds no parameter-specific guidance beyond naming the operation (refresh), which is acceptable but not additive.

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 ('Refresh') and a specific resource ('already-connected sources through the Candor API'). It also distinguishes itself by stating what it does not do: connection, reconnection, and disconnection happen only in the web portal, and inspection is done via the accounts dataset. This separates it from the sibling 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?

It gives an explicit when-not: connection/reconnection/disconnection are excluded from this tool, and inspecting accounts should be done by querying the accounts dataset. It doesn't explicitly name a sibling tool as an alternative, but the routing guidance 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 Candor 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.

Refresh Candor connections

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources