Skip to main content
Glama

Wellspent: fee-only financial advisors

List Wellspent specialties, audiences, and regions

list_specialties_and_audiences
Read-onlyIdempotent

Use this when you need valid slugs for search_fee_only_advisors, or the person asks what they can search by. Lists planning specialties, client audiences, and regions (US states and Canadian provinces that have advisors).

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_specialties_and_audiences"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
regionsYes
audiencesYes
attributionYes
specialtiesYes

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. First observed

TDQS

A4.5/5.0
Behavior4/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 covered. The description adds genuinely new behavioral context: the returned regions are restricted to those that actually have advisors, which tells the agent the list is a filtered subset rather than a full geographic enumeration.

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?

Two sentences, with the usage trigger front-loaded before the content enumeration. No filler, no restatement of the title, and the parenthetical about provinces is a compact qualifier rather than a new sentence.

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 shape need not be explained, and the annotations carry the safety profile. The description still covers the one thing structured fields cannot: what the tool is for and how it feeds the search tool. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100% and both parameters (context, conversation_id) are optional analytics fields fully documented in the schema. The description adds no parameter guidance, but with zero required parameters and complete schema text there is little left for it to explain.

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?

The description names a specific verb (Lists) and three concrete resources (planning specialties, client audiences, regions), then scopes regions precisely to 'US states and Canadian provinces that have advisors'. This makes it unmistakably the reference/lookup tool rather than one of the advisor-search siblings.

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?

It gives a clear trigger: when valid slugs are needed for search_fee_only_advisors, or when the person asks what they can search by. That routes the agent to the right sibling for the most common dependency. It stops short of stating when *not* to call it or naming the other siblings it is not, so a 4 rather than a 5.

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