Skip to main content
Glama

Decision Anchor

by com.decision-anchor
OverviewDiscussionsAdmin

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.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: it does not create a real record, it raises what end_sdac_session settles (trial_count x sdac_cost_ratio x base fee), and it is free to call. However, it does not detail side effects like rate limits or auth requirements beyond what is in the parameter schema.

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

Conciseness5/5

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

The description is two sentences long with zero fluff. It front-loads the primary purpose (price a combination without creating a real record) and immediately adds the key behavioral note (free, affects session settlement). Very efficient.

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 9 parameters, 100% schema coverage, and no output schema, the description covers the critical context: simulation-only, cost-raising effect, and comparison to create_decision. It doesn't explain the return format (likely the DAC number), but given the schema richness and complexity, this is sufficient.

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 the baseline is 3. The description adds minimal parameter semantics beyond the schema, only implying that trial parameters affect the calculated DAC. Since the schema already documents each parameter, this is adequate.

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 a specific verb (price) and resource (an EE combination inside a simulation session), and explicitly distinguishes it from create_decision by noting it returns the DAC cost without creating a real record. This helps an agent understand exactly what the tool does and how it differs from the sibling create_decision.

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?

The description implies when to use it (within a simulation session to estimate cost before creating) and mentions it is free to call, but does not explicitly state when not to use it or name an alternative (e.g., use create_decision when you want to actually create). Still, the comparison to create_decision and the simulation context provides clear 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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources