Skip to main content
Glama

AINumbers Fintech Intelligence Suite

Consultation Response Tracker

compute_consultation_response_tracker
Read-onlyIdempotent

Consultation Response Tracker: OpenChainGraph compute node (analytics_mandate). Deterministic OpenChainGraph compute node. By default (compute:"auto") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:"browser" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic or anonymised inputs only. Exports an AP2 artifact with execution_hash for chain provenance. Open at: https://ainumbers.co/tools/678-consultation-response-tracker.html FV-status (published/proven/still-trusted for this spec): /fv-status/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compute_consultation_response_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
computeNoCompute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always return browser delegation URL. gpu:true nodes always delegate.
parent_hashesNoexecution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
parent_tool_idsNotool_id values matching parent_hashes, in the same order.
policy_parametersNoInput parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "server". See the tool's manifest for field names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

C2.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds real value on top: inputs are processed transiently and not stored or logged, gpu:true nodes always delegate to the browser, and output is an AP2 artifact carrying execution_hash for chain provenance. The data-retention and delegation behavior is exactly the kind of context annotations cannot express, though some of it duplicates the compute parameter description.

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

Conciseness2/5

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

The opening clause restates the title, then the text spends most of its length on execution-mode boilerplate already present in the schema. The closing FV-status URL with a 64-character hash and offline-verification note is irrelevant to deciding whether and how to invoke the tool.

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

Completeness2/5

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

With four parameters, a nested free-form object, and no output schema, the description should explain what policy_parameters must contain and what the response looks like. Instead it defers to an external manifest and only mentions the AP2 artifact hash, leaving the actual decision inputs and return shape unexplained.

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 compute, parent_hashes, parent_tool_ids, and policy_parameters are all documented in the schema itself. The description adds no field-level meaning and leaves policy_parameters field names to 'the tool's manifest', so it earns only the baseline for fully covered schemas.

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

Purpose2/5

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

The description identifies the tool as an 'OpenChainGraph compute node (analytics_mandate)' and says it 'computes the response', but never states what a consultation response tracker actually analyzes or what domain object it operates on. Most of the text describes execution infrastructure and provenance rather than the tool's function, so an agent cannot tell what result to expect or how it differs from the many other compute_* siblings.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no named alternative, and no prerequisite or exclusion statements. The only directive is 'Use synthetic or anonymised inputs only', which is a data-handling constraint rather than a routing rule; the compute-mode explanation merely restates the schema enum.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.