Skip to main content
Glama

get_position_health

Read-onlyIdempotent

Use as a compatibility alias to retrieve agent activity and performance metrics by wallet address; the current endpoint does not return DeFi position APR, PnL, impermanent loss, or rebalance health.

Instructions

[Capability: paid_ready; tier: pioneer_plus; API: /api/v1/agent/performance; authority: /api/v1/agent/status] Compatibility alias for agent activity/performance metrics. Current endpoint does not return DeFi position APR, PnL, impermanent loss, or rebalance health.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "get_position_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.0.0

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds important behavioral context beyond annotations: it discloses that the tool is a compatibility alias and that the current endpoint does not return DeFi position health metrics despite the tool name. This prevents an agent from misinterpreting the output, though auth requirements and rate limits remain unmentioned.

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 two sentences with the key limitation front-loaded in the second sentence. The bracketed capability/API metadata is dense but potentially useful for routing. It is appropriately sized for a compatibility shim, though the metadata prefix slightly competes with the core caveat.

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 one-parameter, read-only tool without an output schema, the description does well to disclose the negative scope but leaves key gaps. It does not explain what the tool actually returns, nor does it clarify the address parameter. Given the misleading name, more explicit routing and output expectations would be needed for a higher score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has one required parameter, address, and schema description coverage is 0%. The schema only provides a 0x-pattern, and the description does not mention the parameter at all. It fails to clarify whether the address is a wallet, agent, or contract address, which is important for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description calls itself a 'compatibility alias for agent activity/performance metrics,' which identifies the underlying resource but not a specific operation. It explicitly rules out DeFi position APR, PnL, impermanent loss, and rebalance health, which is useful given the misleading tool name. However, it does not clearly state what metrics the tool actually returns or distinguish it from sibling tools like get_agent_performance or get_agent_activity.

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?

There is no explicit guidance on when to use this tool versus get_agent_performance, get_agent_activity, or get_agent_events. 'Compatibility alias' weakly implies legacy callers should use it, but no conditions, alternatives, or exclusions are stated. An agent would have to guess whether this is the right tool for activity/performance data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools