Skip to main content
Glama

Decision Anchor

by com.decision-anchor
OverviewDiscussionsAdmin

Observe Environment

observe_environment
Destructive

Observe aggregate environment statistics: active agents, total decisions recorded, activity density. Requires auth_token. The cost comes from the current ARA observation pricing and is paid via x402; Trial does not cover ARA observation. The amount charged is returned in the response as dac_charged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
auth_tokenNoYour DA agent auth token. Optional when this connection already carries one (Authorization: Bearer header on the remote server, or DA_AUTH_TOKEN for a local stdio server); an explicit value takes precedence.
payment_signatureNoOptional x402 payment payload (base64), required only for paid calls. Omit it on the first call: the tool returns the payment challenge. Sign that challenge with your own wallet, then call this tool again with identical arguments plus this field. Decision Anchor never holds your key and never signs on your behalf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / auth_token / description
      Previous value: -"Your DA agent auth token"New value: +"Your DA agent auth token. Optional when this connection already carries one (Authorization: Bearer header on the remote server, or DA_AUTH_TOKEN for a local stdio server); an explicit value takes precedence."
    • removedInput schema / required
      Removed value: -[
-  "auth_token"
-]
  2. Changed1 schema field changed
    • addedInput schema / properties / payment_signature
      Added value: +{
+  "description": "Optional x402 payment payload (base64), required only for paid calls. Omit it on the first call: the tool returns the payment challenge. Sign that challenge with your own wallet, then call this tool again with identical arguments plus this field. Decision Anchor never holds your key and never signs on your behalf.",
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / auth_token
      Added value: +{
+  "description": "Your DA agent auth token",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "auth_token"
+]
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations mark this non-read-only and destructive, and the description corroborates that by disclosing the paid nature of the call: cost comes from ARA observation pricing, payment via x402, Trial does not cover ARA observation, and the charge is returned as dac_charged. This adds real behavioral context beyond the safety hints, though it does not explain the two-step challenge/sign cycle's failure modes.

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 what is observed, then moves to prerequisites, cost, and the single return value. Four compact sentences with no filler, though the payment sentence is dense enough to require a second read.

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 paid tool with no output schema, the definition covers auth, pricing source, payment protocol, trial exclusion, and the returned dac_charged field, which is close to complete. Missing only the multi-call payment flow already hinted at in the schema.

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 both parameters are already documented in detail, giving a baseline of 3. The description's only parameter claim is that auth_token is 'Required', which slightly conflicts with the schema's statement that it is optional when a bearer header or DA_AUTH_TOKEN is present.

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?

States a specific verb (observe) and resource (aggregate environment statistics), then enumerates what is observed: active agents, total decisions, activity density. This distinguishes it from siblings like observe_pattern and get_environment_anomaly, though it never names those alternatives explicitly.

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

Usage Guidelines3/5

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

No explicit when-to-use versus-when-to-use-alternative guidance is given. It does supply a useful procedural rule (omit payment_signature on the first call to receive the challenge), which is genuine invocation guidance, but the reader must infer when this tool beats observing patterns or anomalies.

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

All Decision Anchor toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources