Skip to main content
Glama

Save a fund list

set_fund_list
DestructiveIdempotent

Save the client's own list of funds under name, such as the funds an advisor works with. Replaces a list of the same name (any case); an empty asset_ids deletes it.

Funds and ETFs only, by asset_id from screen_funds or find_assets. screen_funds takes
the list by name in ``fund_lists``, to screen within it or list its funds.

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": {
      "name": "<name>",
      "asset_ids": "<asset_ids>"
    },
    "name": "set_fund_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
asset_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare destructiveHint=true; the description makes that concrete by explaining that a same-named list (matched case-insensitively) is replaced and that an empty asset_ids deletes the list entirely. It also discloses the validation constraint that only funds and ETFs are accepted, which is behavior not derivable from the 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.

Conciseness5/5

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

Three tight sentences: purpose and replacement semantics first, then the destructive edge case, then valid input sources and the downstream consumer. No filler, and the most decision-relevant facts are front-loaded.

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

Completeness4/5

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

For a two-parameter mutation with rich annotations and no output schema, the description covers naming, replacement, deletion, and valid asset types. The only small gap is whether the call returns the stored list or a confirmation, which is not needed to invoke it 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 0%, so the description carries the full load and mostly does: it explains that ``name`` is the replacement key (case-insensitive) and that ``asset_ids`` holds fund/ETF asset ids sourced from sibling tools, with an empty array meaning delete. It stops short of details like ordering, duplicate ids, or whether the name's casing is preserved.

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: 'Save the client's own list of funds under ``name``', with a concrete example of what such a list is. It also distinguishes this tool from the retrieval siblings by pointing to find_assets and screen_funds as the source of asset_ids and as the consumer of the saved list.

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?

Gives clear routing context: asset_ids must come from screen_funds or find_assets, and screen_funds consumes the saved list via the ``fund_lists`` argument. It does not state explicit exclusions or when to prefer a different save tool, but the surrounding workflow is unambiguous.

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