Skip to main content
Glama

Decision Anchor

by com.decision-anchor
OverviewDiscussionsAdmin

Publish Marketplace Tool

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 / ara_connections / items / properties / observation_type / description
      Previous 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)"New value: +"Observation kind this tool interprets. The (observation_type, resolution_level) pair must exist in the ARA price list; otherwise registration is rejected with 400 INVALID_ARA_CONNECTION."
    • changedInput schema / properties / ara_connections / items / properties / resolution_level / description
      Previous value: -"1-3 depending on type (default 1)"New value: +"Resolution level for that observation type (default 1). The levels available per type come from the ARA price list."
  2. 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"
+]
  3. 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"
+]
  4. 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"
  5. 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"
+]
  6. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the mutation profile is partly covered. The description adds the revenue/pricing behavior, which is useful context, but omits prerequisites such as the auth token requirement and the fact that registration is rejected with 400 INVALID_ARA_CONNECTION for invalid connections (that detail lives only in the 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?

Two compact sentences with the core action front-loaded and the incentive second. No filler, no redundancy with the title.

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

Completeness3/5

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

For a mutation tool with no output schema and a fully documented input schema, the description is adequate but thin: it never mentions auth requirements, validation failure modes, or what a successful registration returns. The structured fields carry most of the load, leaving the description minimally viable.

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 schema already documents tool_name, price_dac, ara_connections and the layer enum. The description only reinforces the DAC pricing notion and adds nothing about the layered/ARA connection syntax beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb and resource: 'Publish a tool you built to the marketplace.' This clearly distinguishes it from siblings like purchase_tool and list_tools, and the secondary sentence clarifies the monetization outcome. It stops short of naming sibling alternatives explicitly, but the action is unambiguous.

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?

The description says what happens (price in DAC, earn revenue) but gives no when-to-use guidance, no prerequisites, and no mention of the alternative purchase_tool. An agent gets no help deciding under what circumstances registration is appropriate versus other marketplace actions.

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