Skip to main content
Glama

Candor Finance

by money.candor
OverviewDiscussionsAdmin

Inspect Candor changes

candor_changes

Inspect computed comparisons for spending, income, recurring payments, account terms, and investment positions, with basis handles and coverage caveats. Spending and income use inclusive since/until and comparison_since/comparison_until date ranges and compare recorded posted totals, not normalized rates. Without ranges the last complete UTC calendar month is compared with the preceding month; the response reports both date ranges. limit trims output items and never changes the financial comparison. Source history may be incomplete; capped evidence suppresses spending and income comparisons. Use candor_open for new activity and current attention, candor_get for an exact record, candor_query for dated dataset rows, and candor_snapshot for scoped analysis across datasets. This read records action history and an audit event using reason, but does not advance the shared opening checkpoint, mark activity seen, resolve attention, or consume due notes. Acknowledge a processed opening separately through its open.acknowledge next action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum change items to return, from 1 to 1000; defaults to 25. Only trims output, never the comparison evidence.
sinceNoInclusive start of the current range (YYYY-MM-DD). Supply all four range dates for spending or income comparisons.
untilNoInclusive end of the current range (YYYY-MM-DD).
domainNoRestrict to one change domain; omitted or all includes every supported domain. Values: all, spending, income, recurring, account_terms, investments.
reasonNoConcise 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_keyNoOptional 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.
parent_actionNoExisting 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.
comparison_sinceNoInclusive start of the comparison range (YYYY-MM-DD).
comparison_untilNoInclusive end of the comparison range (YYYY-MM-DD).
account_identity_idNoRestrict changes to one durable account identity before applying history caps. This scope applies to every domain; for investments it reads that account's own position observations, so a busy vault cannot crowd the account out of the capped read.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
actionNo
errorsYes
statusYes
metadataNo
warningsYes
request_idYes
generated_atYes
next_actionsYes
user_messageNo
data_freshnessNo
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / account_identity_id / description
      Added value: +"Restrict changes to one durable account identity before applying history caps. This scope applies to every domain; for investments it reads that account's own position observations, so a busy vault cannot crowd the account out of the capped read."
    • addedInput schema / properties / comparison_since
      Added value: +{
+  "description": "Inclusive start of the comparison range (YYYY-MM-DD).",
+  "type": "string"
+}
    • addedInput schema / properties / comparison_until
      Added value: +{
+  "description": "Inclusive end of the comparison range (YYYY-MM-DD).",
+  "type": "string"
+}
    • addedInput schema / properties / domain / description
      Added value: +"Restrict to one change domain; omitted or all includes every supported domain. Values: all, spending, income, recurring, account_terms, investments."
    • removedInput schema / properties / inline_response
      Removed value: -{
-  "description": "Return the full response payload in this MCP tool result instead of a resource link. Use only when the client can materialize large tool results into a code sandbox; the response may be very large.",
-  "type": "boolean"
-}
    • addedInput schema / properties / limit / description
      Added value: +"Maximum change items to return, from 1 to 1000; defaults to 25. Only trims output, never the comparison evidence."
    • 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 / since
      Added value: +{
+  "description": "Inclusive start of the current range (YYYY-MM-DD). Supply all four range dates for spending or income comparisons.",
+  "type": "string"
+}
    • 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."
    • addedInput schema / properties / until
      Added value: +{
+  "description": "Inclusive end of the current range (YYYY-MM-DD).",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "reason"
-]
  2. Changed3 schema fields changed
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +1000
    • addedOutput schema / properties / metadata / properties
      Added value: +{
+  "view_url": {
+    "format": "uri",
+    "type": "string"
+  }
+}
    • removedOutput schema / properties / metadata / propertyNames
      Removed value: -{
-  "type": "string"
-}
  3. Changed1 schema field changed
    • addedOutput schema / properties / metadata
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  4. Changed2 schema fields changed
    • 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"
+]
  5. Changed2 schema fields changed
    • 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"
-}
  6. Changed2 schema fields changed
    • 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"
+}
  7. Changed2 schema fields changed
    • 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"
  8. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Even though annotations are sparse, the description discloses the tool's side-effect profile: it records action history and an audit event using reason, but does not advance the shared opening checkpoint, mark activity seen, resolve attention, or consume due notes. It also explains default date-range behavior and source-history incompleteness, going well beyond what the annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence earns its place: purpose, default behavior, limitations, sibling routing, and side-effect caveats are all covered. The main purpose is front-loaded, though the density of caveats makes it heavier than strictly necessary.

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?

Given 10 parameters, existing output schema, and side-effecting behavior, the description covers defaults, parameter semantics, side effects, and sibling distinctions comprehensively. An agent has enough context to call the tool correctly without needing other sources.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaningful semantics: since/until and comparison_since/comparison_until are inclusive and compare posted totals rather than normalized rates, the default range behavior is defined, and limit only trims output rather than affecting the comparison. This goes beyond the individual parameter descriptions.

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 names the specific verb 'Inspect computed comparisons' and enumerates the supported domains: spending, income, recurring payments, account terms, and investment positions. It also differentiates itself by naming sibling tools for different purposes, so an agent can distinguish it without opening other schemas.

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

Usage Guidelines5/5

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

The description explicitly routes to alternatives: candor_open for new activity and current attention, candor_get for exact records, candor_query for dated rows, and candor_snapshot for scoped cross-dataset analysis. It also clarifies behavioral boundaries such as 'limit trims output items and never changes the financial comparison' and conditions like capped evidence suppressing comparisons.

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

All Candor 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