Skip to main content
Glama

Decision Anchor

by com.decision-anchor
OverviewDiscussionsAdmin

Run Simulation Trial

run_sdac_trial

Price an EE combination inside a simulation session without creating a real record. Returns the DAC the same combination would cost on create_decision. Free to call; each trial raises what end_sdac_session settles (trial_count x sdac_cost_ratio x base fee).

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.
session_idYesActive sDAC session ID from create_sdac_session
access_classNoOptional: read-access class
delegation_stateNoOptional: delegation responsibility state (affects DAC)
ee_retention_periodNoHow long the record would be retainedmedium
ee_responsibility_scopeNoResponsibility scopestandard
content_disclosure_scopeNoOptional: external exposure scope (affects DAC)
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",
-  "session_id"
-]New value: +[
+  "session_id"
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / access_class / description
      Previous value: -"Optional — read-access class"New value: +"Optional: read-access class"
    • changedInput schema / properties / content_disclosure_scope / description
      Previous value: -"Optional — external exposure scope (affects DAC)"New value: +"Optional: external exposure scope (affects DAC)"
    • changedInput schema / properties / delegation_state / description
      Previous value: -"Optional — delegation responsibility state (affects DAC)"New value: +"Optional: delegation responsibility state (affects DAC)"
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only give readOnlyHint=false/destructiveHint=false; the description adds substantive context beyond them: no real record is created, the call is free upfront, and each trial accrues cost that end_sdac_session settles (trial_count x sdac_cost_ratio x base fee). This deferred-cost behavior is exactly the kind of trait an agent cannot infer from annotations. It omits return/pagination detail, keeping it at 4.

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 tight sentences, front-loaded with the core action and the no-persist guarantee, then the return value, then the cost model. Each sentence carries distinct information; slightly dense but no filler.

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?

With no output schema, the description correctly explains the return value (the DAC the combination would cost on create_decision). It also ties the tool into the session lifecycle via end_sdac_session. Complete enough to call safely, though it does not describe the session-state requirements in more detail.

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% with enums documented for all optional parameters, so the schema carries the parameter burden. The description adds the concept of an 'EE combination' and links outputs to DAC, but does not clarify any individual parameter beyond the schema. Baseline 3 applies.

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+resource ('Price an EE combination inside a simulation session') and immediately contrasts it with the sibling create_decision ('without creating a real record'). An agent can distinguish this from create_decision without opening either schema.

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 frames the use context: dry-run pricing inside an active sDAC session vs. actually calling create_decision. It does not include an explicit 'when-not-to-use' exclusion, but the alternative is named implicitly and the session/end_sdac_session coupling gives strong situational guidance.

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