Skip to main content
Glama

Decision Anchor

by com.decision-anchor
OverviewDiscussionsAdmin

Observe Pattern

observe_pattern
Destructive

Observe pattern-level EE distributions and action-type breakdowns across agents. 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
typeYesPattern type to observe
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."
    • changedInput schema / required
      Previous value: -[
-  "type",
-  "auth_token"
-]New value: +[
+  "type"
+]
  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. Changed2 schema fields changed
    • addedInput schema / properties / auth_token
      Added value: +{
+  "description": "Your DA agent auth token",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "type"
-]New value: +[
+  "type",
+  "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 already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered by structured data. The description adds meaningful context beyond that: it requires auth_token, is billed at current ARA observation pricing via x402, is excluded from Trial coverage, and returns the charge as dac_charged. It still doesn't explain why an 'observe' call is flagged destructive, but the added payment/auth behavior is substantive.

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?

Three sentences, front-loaded with what the tool observes, then auth, then billing. Every sentence carries information; only minor phrasing ('The cost comes from...') is slightly loose.

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, auth-gated observation tool with no output schema, the description covers the essentials an agent needs: auth requirement, payment flow, trial exclusion, and the returned charge field. The main remaining gap is the unexplained destructive annotation and the lack of sibling routing guidance.

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 auth_token, payment_signature, and type are already fully documented in the schema, making 3 the baseline. The description reinforces the auth requirement and names the dac_charged return field but adds no syntax or format detail beyond the schema.

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 states a specific verb and resource: 'Observe pattern-level EE distributions and action-type breakdowns across agents,' which is concrete and matches the 'type' enum. It does not, however, differentiate itself from distribution-oriented siblings such as get_self_classification_distribution or observe_environment, so an agent isn't told which observation tool to reach for.

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?

It gives real preconditions – auth_token required, paid via x402, and Trial does not cover ARA observation – which is more than nothing. But it never states when to prefer this tool over the many sibling observation/distribution tools, so usage selection is left implied.

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