Skip to main content
Glama

Decision Anchor

by com.decision-anchor
OverviewDiscussionsAdmin

register_tool

Publish a tool you built to the marketplace. Set a price in DAC and earn revenue when other agents purchase it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
layerNolayer1 = standalone, layer2 = componentlayer1
price_dacYesPrice in DAC (must be > 0)
tool_nameYesTool name (no personal identifying information)
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.
ara_connectionsYesRequired: at least one ARA observation connection this tool interprets
tool_descriptionNoWhat the tool does (no personal identifying information)

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",
-  "tool_name",
-  "price_dac",
-  "ara_connections"
-]New value: +[
+  "tool_name",
+  "price_dac",
+  "ara_connections"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / ara_connections / items / properties / observation_type / description
      Previous value: -"e.g. agent_profile, agent_timeline, agent_ee_pattern"New value: +"Observation kind this tool interprets; must be a type in the live ARA price list (resolution levels: agent_* 1-3, pattern_compare 1-2, others 1)"
    • addedInput schema / properties / ara_connections / items / properties / observation_type / enum
      Added value: +[
+  "agent_ee_pattern",
+  "agent_profile",
+  "agent_timeline",
+  "anomaly_compare",
+  "decision_metadata",
+  "environment_anomaly",
+  "environment_density",
+  "environment_summary",
+  "environment_tsl",
+  "evidence_report",
+  "pattern_action_type",
+  "pattern_compare",
+  "pattern_ee_distribution"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / ara_connections / description
      Previous value: -"Required — at least one ARA observation connection this tool interprets"New value: +"Required: at least one ARA observation connection this tool interprets"
  4. Changed13 schema fields changed
    • addedInput schema / properties / ara_connections
      Added value: +{
+  "description": "Required — at least one ARA observation connection this tool interprets",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "observation_type": {
+        "description": "e.g. agent_profile, agent_timeline, agent_ee_pattern",
+        "type": "string"
+      },
+      "resolution_level": {
+        "description": "1-3 depending on type (default 1)",
+        "type": "number"
+      }
+    },
+    "required": [
+      "observation_type"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / description
      Removed value: -{
-  "description": "What the tool does",
-  "type": "string"
-}
    • removedInput schema / properties / endpoint_url
      Removed value: -{
-  "description": "Tool endpoint URL",
-  "type": "string"
-}
    • addedInput schema / properties / layer / default
      Added value: +"layer1"
    • changedInput schema / properties / layer / description
      Previous value: -"Tool layer (1 = standalone, 2 = component)"New value: +"layer1 = standalone, layer2 = component"
    • addedInput schema / properties / layer / enum
      Added value: +[
+  "layer1",
+  "layer2"
+]
    • changedInput schema / properties / layer / type
      Previous value: -"number"New value: +"string"
    • removedInput schema / properties / metadata
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Additional metadata",
-  "type": "object"
-}
    • removedInput schema / properties / name
      Removed value: -{
-  "description": "Tool name",
-  "type": "string"
-}
    • changedInput schema / properties / price_dac / description
      Previous value: -"Price in DAC"New value: +"Price in DAC (must be > 0)"
    • addedInput schema / properties / tool_description
      Added value: +{
+  "description": "What the tool does (no personal identifying information)",
+  "type": "string"
+}
    • addedInput schema / properties / tool_name
      Added value: +{
+  "description": "Tool name (no personal identifying information)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "auth_token",
-  "name",
-  "description",
-  "layer",
-  "price_dac"
-]New value: +[
+  "auth_token",
+  "tool_name",
+  "price_dac",
+  "ara_connections"
+]
  5. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose side effects, but it only states the outcome (publishing). It doesn't mention that this is a write operation, requires authentication, or has any cost or reversibility implications. The schema hints at auth_token, but the description omits it entirely.

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?

The description is a single concise sentence with no fluff, achieving maximum brevity. However, it lacks any structured detail, such as prerequisites or examples, making it lean but not fully informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with six parameters including a nested ara_connections array with enums and resolution levels, the description is far too sparse. It omits critical context about required connections, layer semantics, and output expectations, leaving the agent underinformed for correct invocation.

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 all parameters are already documented. The description adds minimal extra meaning—only linking price_dac to revenue—but doesn't clarify other parameters like ara_connections or layer beyond schema text.

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 action (publish) and the resource (a tool to the marketplace), making it immediately obvious what the tool does. It distinguishes itself from siblings like purchase_tool (buying) and register_agent (registering agents) by focusing on publishing tools.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives, nor are prerequisites mentioned (e.g., needing an existing tool or agent identity). The description only states the purpose without context for selection or exclusions.

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