Skip to main content
Glama

Antevo Wealth

List capabilities

list_capabilities
Read-onlyIdempotent

What this Antevo Wealth connector exposes — the whole wealth surface (portfolio, risk, credit, real assets, markets, equity & technical analysis, geopolitics, watchlist, goals, today, family, documents, succession readiness, and a wealth map drawn from what you say) behind a single connection.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties
      Removed value: -{
      -  "result": {
      -    "title": "Result",
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "result"
      -]
    • changedOutput schema / title
      Previous value: -"list_capabilitiesOutput"New value: +"list_capabilitiesDictOutput"
  2. First observed

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context beyond that – nothing about whether the result is static or entitlements-dependent, whether it can vary by household/account scope, or what a 'wealth map drawn from what you say' implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence, which is efficient in budget, but it is front-loaded with a marketing framing ('What this Antevo Wealth connector exposes') rather than the operation, and then spends its length on a 14-item parenthetical domain list. That list is the useful part but arrives after the vague clause, and much of it duplicates sibling tool names an agent can already see.

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

Completeness5/5

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

For a parameterless, read-only discovery call with an output schema present to describe return values, the description only needs to convey surface breadth – which the domain enumeration does. An agent knows what territory the connector covers without needing return-format detail the schema supplies.

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

Parameters4/5

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

The tool takes zero parameters with 100% schema coverage, so there are no parameter semantics for the description to carry. Baseline for a parameterless tool is 4; the description neither helps nor harms here.

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 says what the connector 'exposes' and enumerates concrete domains (portfolio, risk, credit, equity analysis, succession readiness, wealth map), which is more specific than a tautology. But it never states the tool's actual action or return – a list of what? Tool names, endpoints, feature flags? The verb is implied ('exposes'), so an agent must guess the output shape from the output schema rather than the prose.

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 on when to call this versus the 39 siblings; nothing like 'call this first to discover which tools your plan enables' or 'use get_brief for a state snapshot instead'. The enumeration of domains is not a usage condition, and there are no exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources