Skip to main content
Glama

Manawa Terminal

Create watchlist

create_watchlist

Create a watchlist with the given name and ticker symbols.

Args:
    name: Watchlist name
    symbols: List of stock symbols (e.g. ["AAPL", "MSFT"])

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>",
      "symbols": "<symbols>"
    },
    "name": "create_watchlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
symbolsYes
strategy_idNoStrategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / strategy_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Strategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.",
      +  "title": "Strategy Id"
      +}
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered, but the description adds nothing behavioral on top: no indication of what happens on duplicate names, whether symbols are validated, how strategy_id scoping behaves, or what is returned. The 'Args' block merely restates schema fields rather than adding context.

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?

The first sentence is front-loaded and sufficient; the Args block is short but largely redundant with the schema field names. It is efficiently sized overall, just with some duplicated information.

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

Completeness3/5

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

Because an output schema exists, return values need not be described. However, for a mutation tool that creates a named entity, the description should say something about name uniqueness or how strategy_id ties the watchlist to a strategy; that context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 33%, but the description does document both required parameters and adds a concrete example for symbols (["AAPL", "MSFT"]), which the schema lacks. The third parameter, strategy_id, is left entirely to its schema description, so the description covers the essentials without fully compensating for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Create a watchlist') plus the two required inputs, so an agent knows exactly what the tool produces. It does not, however, distinguish it from the other create_* siblings (create_portfolio, create_screener) or from update_watchlist, so differentiation is left to the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this rather than create_portfolio, create_screener, or update_watchlist, and no prerequisites or exclusions. The agent must infer the choice purely from the tool name.

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