Skip to main content
Glama

Decision Anchor

by com.decision-anchor

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_tokenYesYour DA agent auth token
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. Dates show when Glama detected each change.

  1. 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"
  2. 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"
+]
  3. First observed

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the financial aspect (earning revenue) but does not disclose any side effects, such as creating a permanent listing, potential fees, approval requirements, rollback options, or what happens on confirmation. For a marketplace publish action, more detail on side effects and prerequisites (beyond schema) is expected.

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 concise sentences: first states the action (publish to marketplace), second clarifies the pricing and revenue model. It is front-loaded with purpose and contains zero fluff or redundant repetition.

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?

With no output schema and no annotations, the description leaves significant gaps. It does not mention what the tool returns upon success, error scenarios, or steps like approval or validation. It also does not explicitly mention the requirement for ARA connections (though schema states it). The description explains the core action but not the full workflow or expectations, making it incomplete for a tool with 6 parameters and no output schema.

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 covers all parameters with 100% description coverage, so the baseline is 3. The description adds minimal new meaning beyond the schema; it mentions 'Set a price in DAC' which maps to price_dac, but it doesn't clarify auth_token or ara_connections further. The schema already explains these parameters adequately, so no compensation is needed.

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's purpose: publishing a user-built tool to a marketplace, setting a DAC price, and earning revenue from purchases. It uses a specific verb ('Publish') and resource ('tool to the marketplace'), effectively distinguishing it from sibling tools like purchase_tool or list_tools.

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 usage when the agent has built a tool to sell, by saying 'a tool you built'. It does not explicitly mention alternatives or when-not-to-use, but the context makes it obvious this is for registration, not purchasing or listing. It provides clear context but lacks explicit 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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation4/5

Most tools have clear, distinct purposes, but a few overlap in function: get_decision_metadata_distribution and get_self_classification_distribution are both distribution getters, and observe_environment and observe_pattern could be confused. The session status tools (get_ise_status vs get_sdac_session) are also similar.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (create_, get_, list_, observe_, run_, end_, exit_, confirm_, etc.). There are no stylistic deviations or mixed conventions.

Tool Count2/5

With 30 tools, the surface is heavy. Several tools could be consolidated (e.g., the two distribution getters, or the session status getters), making the count feel inflated for the domain's core purpose.

Completeness3/5

The core decision lifecycle (create, confirm, get, list) is covered well, and sessions/observation/marketplace add breadth. However, propose_bilateral lacks a corresponding accept/decline tool, creating a dead end in the bilateral workflow. Also, no way to fetch detailed info on a specific marketplace tool.

Resources