Skip to main content
Glama

create_decision

Use when an action crosses an external boundary: payment, delegation, or agreement with another agent. This anchors the responsibility scope. You say when: before you execute, or after a decision you have already made. Record a tamper-evident decision. This route records self-declared decisions; a declaration that involves a counterparty is made with propose_bilateral instead. Each decision is added to your record trajectory, which you and a counterparty can check against DA's external entry. Omitting the EE axes applies the defaults (medium/basic/internal/standard), equivalent to the EE_standard preset, currently 45 DAC total; the cheapest combination is EE_basic (base fee only, currently 10 DAC). Presets are operator-adjustable; fetch current totals via GET /v1/pricing/ee-presets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateNov1.3.0: required when content_inclusion_flag=1. 7-dimensional decision content metadata.
ee_presetNoOptional EE preset name: expands into the four EE axes and overrides them (fetch active presets via GET /v1/pricing/ee-presets; e.g. EE_basic, EE_standard, EE_high)
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.
request_idNoOptional idempotency key: must be a UUID (the server rejects non-UUID values). Auto-generated if omitted.
decision_atNoOptional: the time your agent itself decided, ISO 8601. The server normalizes it to UTC and that normalized value enters the integrity hash. It must not be later than the anchoring time (400 DECISION_AT_IN_FUTURE). Omit it and no decision time is recorded.
access_classNoOptional: read-access class for the record
dd_unit_typeNoDecision unit typesingle
parent_dd_idNoParent DD ID for lineage tracking
decision_typeYesDecision type
selection_scopeNoOptional: declared scope of the selection
selection_stateNoSelection stateSELECTED
delegation_stateNov1.3.0: delegation responsibility state (DAC add 0/10/30)
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.
ee_retention_periodNoHow long the record is retained. indefinite is declared but not currently available: selecting it is rejected with 403.medium
origin_context_typeYesOrigin context
decision_action_typeYesAction type
content_inclusion_flagNov1.3.0: 0=branch 0 (default, no metadata), 1=branch 1 (template required). No extra DAC, same base fee as branch 0 (the v1.3.0 surcharge was removed in v1.3.14). Branch 1 decisions are the only ones counted toward the anomaly-compare sample.
ee_direct_access_quotaNoDirect access quota (omit to use the server config default)
premium_payment_sourceNoPremium payment source (trial is applied automatically by the server when eligible)
ee_direct_access_periodNoDirect access period (e.g., 30d)30d
ee_responsibility_scopeNoResponsibility scopestandard
content_disclosure_scopeNov1.3.0: external exposure scope (DAC add 0/15/40)
ee_disclosure_format_policyNoDisclosure formatinternal
ee_integrity_verification_levelNoVerification rigorbasic

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: -[
      -  "auth_token",
      -  "decision_type",
      -  "decision_action_type",
      -  "origin_context_type"
      -]New value: +[
      +  "decision_type",
      +  "decision_action_type",
      +  "origin_context_type"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / ee_retention_period / description
      Previous value: -"How long the record is retained (indefinite requires an active indefinite-retention subscription; otherwise 403)"New value: +"How long the record is retained. indefinite is declared but not currently available: selecting it is rejected with 403."
  3. Changed1 schema field changed
    • removedInput schema / properties / dd_declaration_mode
      Removed value: -{
      -  "default": "self_declared",
      -  "description": "Declaration mode",
      -  "enum": [
      -    "self_declared",
      -    "bilateral",
      -    "multi_party"
      -  ],
      -  "type": "string"
      -}
  4. Changed2 schema fields changed
    • addedInput schema / properties / decision_at
      Added value: +{
      +  "description": "Optional: the time your agent itself decided, ISO 8601. The server normalizes it to UTC and that normalized value enters the integrity hash. It must not be later than the anchoring time (400 DECISION_AT_IN_FUTURE). Omit it and no decision time is recorded.",
      +  "type": "string"
      +}
    • removedInput schema / properties / excluded_option_count
      Removed value: -{
      -  "description": "Optional: number of options excluded when deciding (integer >= 0)",
      -  "minimum": 0,
      -  "type": "integer"
      -}
  5. Changed7 schema fields changed
    • changedInput schema / properties / access_class / description
      Previous value: -"Optional — read-access class for the record"New value: +"Optional: read-access class for the record"
    • changedInput schema / properties / content_inclusion_flag / description
      Previous value: -"v1.3.0: 0=branch 0 (default, no metadata), 1=branch 1 (template required). No extra DAC — same base fee as branch 0 (the v1.3.0 surcharge was removed in v1.3.14). Branch 1 decisions are the only ones counted toward the anomaly-compare sample."New value: +"v1.3.0: 0=branch 0 (default, no metadata), 1=branch 1 (template required). No extra DAC, same base fee as branch 0 (the v1.3.0 surcharge was removed in v1.3.14). Branch 1 decisions are the only ones counted toward the anomaly-compare sample."
    • changedInput schema / properties / ee_preset / description
      Previous value: -"Optional EE preset name — expands into the four EE axes and overrides them (fetch active presets via GET /v1/pricing/ee-presets; e.g. EE_basic, EE_standard, EE_high)"New value: +"Optional EE preset name: expands into the four EE axes and overrides them (fetch active presets via GET /v1/pricing/ee-presets; e.g. EE_basic, EE_standard, EE_high)"
    • changedInput schema / properties / ee_retention_period / description
      Previous value: -"How long the record is retained (indefinite requires an active indefinite-retention subscription — otherwise 403)"New value: +"How long the record is retained (indefinite requires an active indefinite-retention subscription; otherwise 403)"
    • changedInput schema / properties / excluded_option_count / description
      Previous value: -"Optional — number of options excluded when deciding (integer >= 0)"New value: +"Optional: number of options excluded when deciding (integer >= 0)"
    • changedInput schema / properties / request_id / description
      Previous value: -"Optional idempotency key — must be a UUID (the server rejects non-UUID values). Auto-generated if omitted."New value: +"Optional idempotency key: must be a UUID (the server rejects non-UUID values). Auto-generated if omitted."
    • changedInput schema / properties / selection_scope / description
      Previous value: -"Optional — declared scope of the selection"New value: +"Optional: declared scope of the selection"
  6. 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"
      +}
  7. Changed2 schema fields changed
    • removedInput schema / properties / ee_direct_access_quota / default
      Removed value: -5
    • changedInput schema / properties / ee_direct_access_quota / description
      Previous value: -"Direct access quota"New value: +"Direct access quota (omit to use the server config default)"
  8. Changed1 schema field changed
    • changedInput schema / properties / content_inclusion_flag / description
      Previous value: -"v1.3.0: 0=branch 0 (default, no metadata), 1=branch 1 (template required, +15 DAC)"New value: +"v1.3.0: 0=branch 0 (default, no metadata), 1=branch 1 (template required). No extra DAC — same base fee as branch 0 (the v1.3.0 surcharge was removed in v1.3.14). Branch 1 decisions are the only ones counted toward the anomaly-compare sample."
  9. Changed4 schema fields changed
    • addedInput schema / properties / access_class
      Added value: +{
      +  "description": "Optional — read-access class for the record",
      +  "enum": [
      +    "self_direct",
      +    "ara_only",
      +    "internal_only"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / ee_preset
      Added value: +{
      +  "description": "Optional EE preset name — expands into the four EE axes and overrides them (fetch active presets via GET /v1/pricing/ee-presets; e.g. EE_basic, EE_standard, EE_high)",
      +  "type": "string"
      +}
    • addedInput schema / properties / excluded_option_count
      Added value: +{
      +  "description": "Optional — number of options excluded when deciding (integer >= 0)",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / selection_scope
      Added value: +{
      +  "description": "Optional — declared scope of the selection",
      +  "enum": [
      +    "single_target",
      +    "multi_target",
      +    "chain_scope",
      +    "global"
      +  ],
      +  "type": "string"
      +}
  10. Changed13 schema fields changed
    • changedInput schema / properties / dd_declaration_mode / enum
      Previous value: -[
      -  "self_declared",
      -  "verified"
      -]New value: +[
      +  "self_declared",
      +  "bilateral",
      +  "multi_party"
      +]
    • changedInput schema / properties / decision_action_type / description
      Previous value: -"Action type (e.g., execute, analyze, agree)"New value: +"Action type"
    • addedInput schema / properties / decision_action_type / enum
      Added value: +[
      +  "execute",
      +  "hold",
      +  "reject",
      +  "depend",
      +  "approve"
      +]
    • changedInput schema / properties / decision_type / description
      Previous value: -"Decision type (e.g., external_interaction, internal_reasoning)"New value: +"Decision type"
    • addedInput schema / properties / decision_type / enum
      Added value: +[
      +  "internal_service",
      +  "external_interaction",
      +  "self_attestation"
      +]
    • changedInput schema / properties / ee_retention_period / description
      Previous value: -"How long the record is retained"New value: +"How long the record is retained (indefinite requires an active indefinite-retention subscription — otherwise 403)"
    • changedInput schema / properties / ee_retention_period / enum
      Previous value: -[
      -  "short",
      -  "medium",
      -  "long"
      -]New value: +[
      +  "short",
      +  "medium",
      +  "long",
      +  "extreme_long",
      +  "indefinite"
      +]
    • changedInput schema / properties / origin_context_type / description
      Previous value: -"Origin context (e.g., external, internal, hybrid)"New value: +"Origin context"
    • addedInput schema / properties / origin_context_type / enum
      Added value: +[
      +  "internal",
      +  "external",
      +  "self",
      +  "mixed"
      +]
    • changedInput schema / properties / premium_payment_source / description
      Previous value: -"Payment source"New value: +"Premium payment source (trial is applied automatically by the server when eligible)"
    • changedInput schema / properties / premium_payment_source / enum
      Previous value: -[
      -  "external",
      -  "earned",
      -  "trial"
      -]New value: +[
      +  "external",
      +  "earned"
      +]
    • changedInput schema / properties / request_id / description
      Previous value: -"Unique idempotency key for this request. Use any UUID or unique string. Auto-generated if omitted."New value: +"Optional idempotency key — must be a UUID (the server rejects non-UUID values). Auto-generated if omitted."
    • changedInput schema / properties / selection_state / enum
      Previous value: -[
      -  "SELECTED",
      -  "DEFERRED",
      -  "REJECTED"
      -]New value: +[
      +  "SELECTED",
      +  "REJECTED",
      +  "ABORTED",
      +  "SILENT",
      +  "NON_DECISION"
      +]
  11. Changed4 schema fields changed
    • addedInput schema / properties / content_disclosure_scope
      Added value: +{
      +  "description": "v1.3.0: external exposure scope (DAC add 0/15/40)",
      +  "enum": [
      +    "owner",
      +    "external",
      +    "public"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / content_inclusion_flag
      Added value: +{
      +  "description": "v1.3.0: 0=branch 0 (default, no metadata), 1=branch 1 (template required, +15 DAC)",
      +  "type": "number"
      +}
    • addedInput schema / properties / delegation_state
      Added value: +{
      +  "description": "v1.3.0: delegation responsibility state (DAC add 0/10/30)",
      +  "enum": [
      +    "none",
      +    "partial",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / template
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "v1.3.0: required when content_inclusion_flag=1. 7-dimensional decision content metadata.",
      +  "properties": {
      +    "call_chain": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "decision_class": {
      +      "enum": [
      +        "payment",
      +        "api_call",
      +        "data_access",
      +        "delegation",
      +        "resource_transfer",
      +        "communication",
      +        "other"
      +      ],
      +      "type": "string"
      +    },
      +    "decision_scale_unit": {
      +      "type": "string"
      +    },
      +    "decision_scale_value": {
      +      "type": "number"
      +    },
      +    "decision_trigger": {
      +      "enum": [
      +        "user_request",
      +        "scheduled",
      +        "event_driven",
      +        "autonomous",
      +        "delegated",
      +        "external_event"
      +      ],
      +      "type": "string"
      +    },
      +    "human_involvement": {
      +      "enum": [
      +        "none",
      +        "notification",
      +        "approval",
      +        "co_decision",
      +        "review"
      +      ],
      +      "type": "string"
      +    },
      +    "self_classification": {
      +      "type": "string"
      +    },
      +    "target_class": {
      +      "enum": [
      +        "internal",
      +        "external",
      +        "third_party",
      +        "subagent",
      +        "human_owner",
      +        "public",
      +        "system"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  12. Changed5 schema fields changed
    • changedInput schema / properties / ee_disclosure_format_policy / default
      Previous value: -"summary"New value: +"internal"
    • changedInput schema / properties / ee_disclosure_format_policy / enum
      Previous value: -[
      -  "internal",
      -  "summary",
      -  "exportable"
      -]New value: +[
      +  "internal",
      +  "shareable",
      +  "exportable"
      +]
    • changedInput schema / properties / ee_integrity_verification_level / default
      Previous value: -"standard"New value: +"basic"
    • changedInput schema / properties / ee_integrity_verification_level / enum
      Previous value: -[
      -  "basic",
      -  "standard",
      -  "enhanced"
      -]New value: +[
      +  "basic",
      +  "enhanced",
      +  "certifiable"
      +]
    • changedInput schema / properties / ee_retention_period / enum
      Previous value: -[
      -  "short",
      -  "medium",
      -  "long",
      -  "permanent"
      -]New value: +[
      +  "short",
      +  "medium",
      +  "long"
      +]
  13. Changed2 schema fields changed
    • changedInput schema / properties / ee_disclosure_format_policy / enum
      Previous value: -[
      -  "none",
      -  "summary",
      -  "exportable"
      -]New value: +[
      +  "internal",
      +  "summary",
      +  "exportable"
      +]
    • addedInput schema / properties / request_id
      Added value: +{
      +  "description": "Unique idempotency key for this request. Use any UUID or unique string. Auto-generated if omitted.",
      +  "type": "string"
      +}
  14. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral burden. It discloses that the decision is tamper-evident, added to a record trajectory, and that omitting EE axes applies defaults. It also mentions pricing and preset adjustability. It does not explicitly state mutation or irreversibility, but 'Record' and 'tamper-evident' imply persistence. It lacks some details like idempotency or payment flow, but those are covered in parameter descriptions.

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

Conciseness3/5

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

The description is a single dense paragraph, reasonably front-loaded with the when-to-use guidance. However, it packs several topics (purpose, timing, alternative, record trajectory, pricing, presets) into one block, making it slightly verbose. It could be broken into clearer sections, but it is not excessively long.

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 tool with 24 parameters, a nested object, and no output schema, the description covers the core usage, the key alternative, pricing implications, and record persistence. It does not explain the return value or the content_inclusion_flag branches, but those are detailed in parameter descriptions. Given the complexity, it is sufficiently complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining EE presets, default costs (45 DAC vs 10 DAC), and how omitting EE axes maps to the EE_standard preset. This is not present in the schema and helps the agent estimate costs and understand defaults.

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?

The description clearly states the tool records a tamper-evident decision when an action crosses an external boundary (payment, delegation, or agreement). It explicitly differentiates from propose_bilateral for counterparty declarations, so an agent knows exactly what this tool does and how it differs from its closest sibling.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance: 'Use when an action crosses an external boundary' and specifies timing ('before you execute, or after a decision you have already made'). It also names the alternative (propose_bilateral) and the condition that selects it (counterparty involvement), leaving no ambiguity.

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.