Skip to main content
Glama

Wellspent: fee-only financial advisors

Get what fee-only advisors typically charge

get_fee_benchmarks
Read-onlyIdempotent

Use this when the person asks what a fee-only financial advisor costs, or whether a price they were quoted is typical. Returns the median and the middle half (25th to 75th percentile) of what fee-only firms charge for ongoing planning per year, a one-time plan, an hourly rate, and a percentage of assets, with how many firms each figure is drawn from. Pass country, and region (a US state slug) for that state's figures next to the country's; states where too few firms publish prices return the country figures only, and there are no provincial figures for Canada. Figures are starting prices that firms publish on their own websites, one per firm, from the latest quarterly edition of the Wellspent fee report: describe them as published prices, not as what the person will pay. State the edition and cite "Source: Wellspent fee report, find.wellspent.co" with the report's url.

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": {
      "country": "<country>"
    },
    "name": "get_fee_benchmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOptional US state or Canadian province slug (e.g. "california"). Must be in the given country.
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.
countryYes"us" for the United States (US dollars), "ca" for Canada (Canadian dollars).
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
notesYes
regionYes
sourceYes
countryYes
currencyYes
attributionYes
region_feesYesWhat firms in the region charge. Null when no region was given or too few firms there publish prices.
region_nameNo
country_feesYesWhat fee-only firms across the country charge.
advice_only_feesNoThe same, for firms that plan without managing investments.
how_firms_chargeNoUS and Canada together: of firms whose website says how they charge, the share charging each way. A firm can charge more than one way.
no_asset_minimumNoOf the firms that state an asset minimum, the share that have none. US only.
region_no_asset_minimumNo

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.6/5.0
Behavior5/5

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

Goes well beyond the supplied annotations. It discloses the data's provenance (latest quarterly Wellspent fee report, published starting prices, one per firm), the fallback behavior for thin state samples, the absence of Canadian provincial figures, and the communication constraint to describe them as published prices rather than expected costs.

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?

Front-loaded with the when-to-use trigger, then the return shape, then parameter behavior, then data caveats and citation instructions. It is dense but every sentence carries operational value for an agent that must caveat and cite the figures; only minor tightening is possible.

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?

An output schema exists so return values need not be explained. For a read-only benchmark tool, the description covers data source, edition, geographic fallbacks, interpretive constraints, and required citation, leaving nothing material an agent needs in order to call and present the results correctly.

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 baseline is 3. The description adds real meaning: region returns that state's figures next to the country's, falls back to country-only when too few firms publish, and has no provincial equivalents in Canada. Country's currency meaning is left to the schema, keeping this from a 5.

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: returns median and 25th-75th percentile fees for ongoing planning, one-time plans, hourly rates, and percentage of assets. An agent can distinguish this benchmark tool from sibling advisor-lookup tools like search_fee_only_advisors without opening a schema.

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?

Explicitly names the triggering situations: 'when the person asks what a fee-only financial advisor costs, or whether a price they were quoted is typical.' It does not name a sibling alternative or state when not to use it, so it falls short of the 5 bar, but the usage context is clear.

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