Skip to main content
Glama
Sign In

zFinia Intelligence

by com.zfinia.api
OverviewDiscussionsAdmin

Machine Economy Changes Since

machine_economy_changes_since

Return curated machine-economy developments covering x402 and agent commerce after a supplied cursor or since value. This delta feed includes material additions, corrections and retractions with provenance and nextCursor for caller-managed polling; an empty result is valid. No transaction feed, built-in scheduler, generic web search or exhaustive ecosystem monitoring. Pay 10000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

Input Schema

NameRequiredDescriptionDefault
sinceNoAlias of cursor. Use the previous nextCursor so only later material changes are returned.
cursorNoPrevious nextCursor (opaque or ISO-8601). Required for the paid delta unless since is set. Pass this back on the next poll.
maxItemsNo
include_high_resolutionNoWhen true, paid items include full evidence fields already present on the public newswire item.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "count": {
-      "type": "integer"
-    },
-    "generatedAt": {
-      "type": "string"
-    },
-    "highResolution": {
-      "type": "boolean"
-    },
-    "items": {
-      "type": "array"
-    },
-    "marketMovements": {
-      "type": "object"
-    },
-    "nextCursor": {
-      "type": "string"
-    },
-    "priceAtomic": {
-      "type": "string"
-    },
-    "product": {
-      "type": "string"
-    },
-    "request_id": {
-      "description": "Delivery request identifier; also returned in x-foundry-request-id.",
-      "type": "string"
-    },
-    "schema": {
-      "type": "string"
-    },
-    "schemaVersion": {
-      "type": "string"
-    },
-    "service_id": {
-      "description": "Canonical service identifier.",
-      "type": "string"
-    },
-    "service_version": {
-      "description": "Version of the invoked service.",
-      "type": "string"
-    },
-    "since": {
-      "type": "string"
-    },
-    "truncated": {
-      "type": "boolean"
-    },
-    "usageRights": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "request_id",
-    "service_id",
-    "service_version",
-    "schema",
-    "generatedAt",
-    "since",
-    "nextCursor",
-    "count",
-    "items",
-    "truncated",
-    "usageRights"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed5 schema fields changed
    • 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
  3. Changed4 schema fields changed
    • 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"
+]
  4. Changed3 schema fields changed
    • 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
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the paid nature (10000 atomic USDC on Base via exact x402), that MCP does not pay and instead hands off a challenge, that empty results are valid, and that results include additions, corrections and retractions with provenance.

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?

Front-loads the core purpose and delta semantics before payment details. The later fragments ('No transaction feed...', 'Pay 10000 atomic USDC on Base via exact x402.') are telegraphic but each carries distinct, load-bearing information.

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?

No output schema exists, and the description still explains the return shape (provenance, nextCursor, empty result valid) and the payment handoff flow. Only gap is what maxItems and include_high_resolution do to the response, which the schema partially covers.

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 coverage is 75% and the description reinforces the cursor/since-as-nextCursor pattern already documented in the schema. It adds nothing for maxItems or include_high_resolution, so the description is not compensating beyond what the schema already says.

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?

States a specific verb and resource ('Return curated machine-economy developments covering x402 and agent commerce') plus the delta gating condition (after a supplied cursor or since value). The explicit exclusions ('No transaction feed, built-in scheduler, generic web search') separate it sharply from siblings like x402_endpoint_health and the page_* 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?

Clearly scoped to 'a caller that already has a zFinia cursor' with caller-managed polling semantics stated. The when-not list (no transaction feed, no scheduler, no exhaustive monitoring) does the routing work, though it never names a specific alternative sibling for those excluded needs.

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

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