zFinia Intelligence

Machine Economy Changes Since

machine_economy_changes_since

When your agent already checked zFinia and needs only material machine-economy changes since its last cursor, use this tool. Returns delta items and nextCursor for the next poll; empty items is valid. Pay 10000 atomic USDC on Base via exact x402. MCP does not pay.

Input Schema

TableJSON Schema

Name	Required	Description
`since`	No	Alias of cursor. Use the previous nextCursor so only later material changes are returned.
`cursor`	No	Previous nextCursor (opaque or ISO-8601). Required for the paid delta unless since is set. Pass this back on the next poll.
`maxItems`	No
`include_high_resolution`	No	When true, paid items include full evidence fields already present on the public newswire item.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes
`items`	Yes
`since`	Yes
`schema`	Yes
`product`	No
`truncated`	Yes
`nextCursor`	Yes
`request_id`	Yes	Delivery request identifier; also returned in x-foundry-request-id.
`service_id`	Yes	Canonical service identifier.
`generatedAt`	Yes
`priceAtomic`	No
`usageRights`	Yes
`schemaVersion`	No
`highResolution`	No
`marketMovements`	No
`service_version`	Yes	Version of the invoked service.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 11, 2026
- addedInput schema / anyOf
```
Added value: +[
+  {
+    "required": [
+      "cursor"
+    ]
+  },
+  {
+    "required": [
+      "since"
+    ]
+  }
+]
```
- addedInput schema / properties / cursor / maxLength
```
Added value: +2048
```
- addedInput schema / properties / cursor / minLength
```
Added value: +1
```
- addedInput schema / properties / since / maxLength
```
Added value: +2048
```
- addedInput schema / properties / since / minLength
```
Added value: +1
```

Changed4 schema fields changedSep 11, 2026

addedOutput schema / properties / request_id

Added value: +{
+  "description": "Delivery request identifier; also returned in x-foundry-request-id.",
+  "type": "string"
+}

addedOutput schema / properties / service_id

Added value: +{
+  "description": "Canonical service identifier.",
+  "type": "string"
+}

addedOutput schema / properties / service_version

Added value: +{
+  "description": "Version of the invoked service.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "schema",
-  "generatedAt",
-  "since",
-  "nextCursor",
-  "count",
-  "items",
-  "truncated",
-  "usageRights"
-]New value: +[
+  "request_id",
+  "service_id",
+  "service_version",
+  "schema",
+  "generatedAt",
+  "since",
+  "nextCursor",
+  "count",
+  "items",
+  "truncated",
+  "usageRights"
+]

Changed3 schema fields changedSep 9, 2026
- addedInput schema / properties / cursor / example
```
Added value: +"2026-09-01T00:00:00.000Z"
```
- addedInput schema / properties / include_high_resolution / example
```
Added value: +true
```
- addedInput schema / properties / maxItems / example
```
Added value: +3
```
First observedSep 8, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the disclosure load. It discloses the payment requirement (10000 atomic USDC on Base via x402), that MCP does not pay, and that empty items is a valid response. It omits failure behavior or authorization requirements, so it is solid but not exhaustive.

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?

Four short sentences, each carrying a distinct fact: when to use, what returns, empty-valid, and payment responsibility. There is no verbose prose or schema repetition; it can be skimmed in a few seconds.

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?

The description covers the main loop (cursor → delta → nextCursor), the edge case of empty results, and the cost/payer model. It does not explain how to actually pay via x402, but given the presence of an output schema and detailed parameter coverage, the agent has enough context to call the tool safely.

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 covers most parameters (75%), so the baseline is a 3. The description adds a small amount by framing the cursor as integral to the polling workflow ('returns delta items and nextCursor for the next poll'), but it does not enrich the meaning of maxItems or the exact relationship between since and cursor beyond what the schema already states.

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?

The description clearly states the tool returns delta items and nextCursor for polling, and scopes it to machine-economy changes after a prior zCursor check. However, it does not explicitly distinguish itself from sibling tools, so an agent must infer that sibling tools are unrelated from their names.

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 opening sentence gives an explicit trigger: use it when the agent has already checked zFinia and needs only material changes since the last cursor. It does not state exclusions or name alternative tools to use when the precondition is not met, missing a small opportunity to route the agent away.

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

All zFinia Intelligence 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.

Resources

Need Help?