Skip to main content
Glama

Wellspent: fee-only financial advisors

Get a fee-only firm's public profile

get_firm_profile
Read-onlyIdempotent

Use this when the person asks about a firm rather than one advisor, or after find_advisor_or_firm_by_name returns a firm. Returns the public record of a firm listed on Wellspent, by the firm slug from find_advisor_or_firm_by_name (the last path segment of the firm's profile_url): where it is, the fee-only advisors Wellspent lists there with their slugs, what the firm's website says it charges, its SEC Form ADV record (assets managed, accounts, employees, how it is paid), and its assets under management over time. Assets changing over time reflects markets as well as clients, and says nothing on its own about the quality of advice. Contact details are not included: share profile_url. Cite "Source: Wellspent, find.wellspent.co" and suggest verifying the firm at its regulatory_lookup link.

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": {
      "slug": "<slug>"
    },
    "name": "get_firm_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe firm's slug, from find_advisor_or_firm_by_name results where kind is "firm".
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
cityNo
feesNoWhat the advisor charges, in one shape for every profile. A null means the fact isn't known, not that the answer is no. stated_by says whose words these are.
nameNo
slugYes
foundYes
notesNo
regionNo
countryNo
messageNo
websiteNo
advisorsNo
locationNo
data_datesNo
sec_recordNoFrom the firm's latest Form ADV. Null when no SEC record is linked to the firm.
attributionYes
profile_urlNo
advisor_countNoFee-only advisors Wellspent lists at the firm.
assets_historyNoThe firm's regulatory assets under management as reported on each Form ADV filing, oldest first. Null when there is no SEC record or no filings with assets.
advisors_truncatedNoTrue when the firm has more advisors than advisors holds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / fees / properties / pricing / properties / asset_minimum / description
      Previous value: -"Minimum investable assets; 0 means no minimum."New value: +"Minimum investable assets; 0 means no minimum. Read it with asset_minimum_scope."
    • addedOutput schema / properties / fees / properties / pricing / properties / asset_minimum_scope
      Added value: +{
      +  "description": "What asset_minimum covers. firm: needed to work with the firm at all. investment_management: needed only to have the firm manage a portfolio. unclear: the firm charges in more than one way and its website doesn't make plain which service the minimum belongs to, so ask the firm. Null when there is no minimum.",
      +  "enum": [
      +    "firm",
      +    "investment_management",
      +    "unclear",
      +    null
      +  ],
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / fees / properties / pricing / required
      Previous value: -[
      -  "ongoing_per_year_from",
      -  "one_time_from",
      -  "hourly_rate",
      -  "aum_percent_first_tier",
      -  "asset_minimum",
      -  "currency"
      -]New value: +[
      +  "ongoing_per_year_from",
      +  "one_time_from",
      +  "hourly_rate",
      +  "aum_percent_first_tier",
      +  "asset_minimum",
      +  "asset_minimum_scope",
      +  "currency"
      +]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent; the description adds substantive behavior: contact details are withheld so profile_url must be shared, an attribution string is required, the agent should suggest verification at the regulatory_lookup link, and AUM-over-time is caveated as reflecting markets rather than advice quality. That is real guidance an agent could not infer from annotations or schema.

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 selection rule before the return contents, which is the right ordering. The middle enumerates returned fields in one long sentence, which edges toward duplicating the output schema, but the caveats and citation instruction that follow all earn their place.

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 no further explanation, and the description covers everything else an agent needs: prerequisite lookup, slug format source, what is deliberately excluded, attribution text, and the verification step. Complete for a read-only profile fetch.

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 still adds an extra derivation path for slug ('the last path segment of the firm's profile_url') beyond the schema's note about find_advisor_or_firm_by_name results. It says nothing extra about context or conversation_id, but those are analytics-only and self-documented.

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 the public record of a firm listed on Wellspent' — and explicitly contrasts with get_advisor_profile via 'when the person asks about a firm rather than one advisor.' The scope (fee-only firms, keyed by slug) is unambiguous.

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?

Gives both a direct trigger ('when the person asks about a firm') and a chained trigger ('after find_advisor_or_firm_by_name returns a firm'), and names the sibling it is not for (advisor-level questions). An agent knows exactly when to select this over the alternatives.

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