Skip to main content
Glama

Wellspent: fee-only financial advisors

Show advisor cards

show_advisor_cards
Read-onlyIdempotent

Use this after search_fee_only_advisors to show up to 8 of its results as cards, in the order given, each with a View profile link to find.wellspent.co. Pass the slugs from the search results. Shows only public Wellspent data. Do not use for advisors that did not come from a Wellspent search.

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": {
      "slugs": "<slugs>"
    },
    "name": "show_advisor_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYesAdvisor slugs from search_fee_only_advisors results.
contextNoOptional, for analytics only. Why are you calling this tool? Describe the goal in general terms in 15 to 25 words, and refer to people by role ("the user") rather than by name. Leave out personal and identifying information.
conversation_idNoOptional, for analytics only. The conversation_id this server returned earlier in this conversation, passed back unchanged so its calls are counted together. Leave it out on the first call.

Output Schema

NameRequiredDescriptionDefault
advisorsYes
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Optional, for analytics only. Why are you calling this tool? Describe the goal in general terms in 15 to 25 words, and refer to people by role (\"the user\") rather than by name. Leave out personal and identifying information.",
      +  "maxLength": 2000,
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Optional, for analytics only. The conversation_id this server returned earlier in this conversation, passed back unchanged so its calls are counted together. Leave it out on the first call.",
      +  "maxLength": 64,
      +  "type": "string"
      +}
  2. Added

TDQS

A4.7/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 by structured data. The description still adds useful behavior beyond that: a hard cap of 8 cards, order preservation, the View profile link target, and that only public Wellspent data is shown. It does not describe what happens if fewer or invalid slugs are supplied, which keeps it short of a 5.

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?

Four short sentences, front-loaded with the primary action, then the constraints, then the exclusion. No restatement of the title and no filler.

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 read-only, single-required-parameter rendering tool with an output schema, everything an agent needs to call it correctly is present: prerequisite, input source, ordering, cap, and link behavior. Return structure is covered by the output schema, so it need not be described.

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?

Schema coverage is 100%, so the baseline is 3; the description earns extra credit by adding ordering semantics ('in the order given'), which the schema does not express, and by restating where slugs originate. It adds nothing about the analytics-only context and conversation_id parameters, but those are already fully documented in the schema.

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?

States a specific verb and resource (show advisor results as cards) plus scope details an agent can act on: up to 8 items, in the given order, each rendered with a View profile link to a named domain. It is clearly distinguishable from search_fee_only_advisors (which produces the results) and from a single-profile lookup, since the output is a card list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the prerequisite tool ('after search_fee_only_advisors') and the exclusion ('Do not use for advisors that did not come from a Wellspent search'), and tells the agent where the input values come from. Both the when-to-use and when-not conditions are stated rather than implied.

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