Skip to main content
Glama
Sign In

Ava Advisor

by fund.ava
OverviewDiscussionsAdmin

Remove from Playlist

remove_from_playlist
DestructiveIdempotent

πŸ”΄ WRITE β€” remove one or more stocks (by ticker) from a playlist (batch). playlist_id from list_playlists. Returns {removed, not_found, item_count} β€” relay not_found (a ticker that wasn't in the playlist) to the user.

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": {
      "playlist_id": "<playlist_id>",
      "tickers": "<tickers>"
    },
    "name": "remove_from_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersYesAva Advisor tickers to remove from the playlist.
playlist_idYesThe playlist's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 destructiveHint=true and idempotentHint=true, so safety is covered. The description adds meaningful context beyond that: it discloses the return shape `{removed, not_found, item_count}` and instructs the agent to relay `not_found` tickers to the user, which is important partial-failure behavior not visible in structured fields.

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?

Extremely compact: two sentences front-load the write nature, action, and scope, then immediately cover return values and user-relay instructions. Every clause carries actionable information with 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 simple two-parameter mutation tool with no output schema, the description supplies everything an agent needs: write semantics, id/parameter sourcing, return shape, and partial-failure handling. No material behavioral gap remains.

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, but the description adds value by noting the operation is batched by ticker and by specifying the source of `playlist_id` (`list_playlists`), which the schema does not mention.

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 ('remove'), resource ('stocks...from a playlist'), and scope ('one or more...by ticker (batch)'). An agent can immediately distinguish this from the sibling add_to_playlist without opening either 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?

Provides a concrete prerequisite by telling the agent to obtain `playlist_id` from `list_playlists`, which prevents a common call failure. It does not explicitly state when not to use this versus add_to_playlist, but the context is clear enough for correct routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ava Advisor toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources