Skip to main content
Glama

Decision Anchor

by com.decision-anchor
OverviewDiscussionsAdmin

get_agent_profile

View an agent's decision profile: their trajectory shape, EE patterns, and activity summary as observed through ARA. Paid via x402; Trial does not cover ARA observation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesAgent ID to observe
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.
payment_signatureNoOptional x402 payment payload (base64), required only for paid calls. Omit it on the first call: the tool returns the payment challenge. Sign that challenge with your own wallet, then call this tool again with identical arguments plus this field. Decision Anchor never holds your key and never signs on your behalf.

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",
-  "agent_id"
-]New value: +[
+  "agent_id"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / payment_signature
      Added value: +{
+  "description": "Optional x402 payment payload (base64), required only for paid calls. Omit it on the first call: the tool returns the payment challenge. Sign that challenge with your own wallet, then call this tool again with identical arguments plus this field. Decision Anchor never holds your key and never signs on your behalf.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses that the operation is viewed rather than mutating, that it incurs x402 payment, and that Trial access is insufficient. It does not elaborate on rate limits or side effects, but for a read-oriented profile tool the payment disclosure is the key behavioral constraint.

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 sentences with no filler. The purpose is front-loaded and the critical payment constraint is stated immediately after, making the essential information easy to parse.

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?

The description names the expected result components (trajectory shape, EE patterns, activity summary), which partially compensates for the missing output schema. Payment prerequisites and parameter details are covered by the schema, so an agent has enough context to invoke the tool correctly.

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 agent_id, auth_token, and payment_signature in detail. The description adds context about the returned profile content but does not materially deepen the meaning of the individual parameters beyond what the schema provides.

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?

Description uses a specific verb ('View') and a specific resource (agent's decision profile), then details what the profile contains: trajectory shape, EE patterns, and activity summary. The 'as observed through ARA' qualifier distinguishes this from similar-looking observational 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 clearly conveys the key usage condition: this is a paid x402 operation and Trial does not cover ARA observation. It gives the agent enough context to know when this tool applies, though it does not explicitly name alternative tools or state when to avoid it.

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