Skip to main content
Glama

equibles

by io.github.daniel3303

Unwatch Instrument

UnwatchInstrument
Destructive

Remove a stock or an option contract from one of the USER's portfolio watchlists. This only removes the watch entry: it never touches a holding, so a stock the portfolio also owns stays exactly as recorded. Confirm with the user before removing.

Address the instrument the way it appears in GetMyPortfolio's Watching section: the ticker for a stock, or the OCC symbol in optionContract for an option.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerNoThe watched stock's ticker. Omit when removing an option by its OCC symbol.
portfolioYesThe portfolio whose watchlist to remove from, by name.
optionContractNoOptional. The watched option's OCC symbol, e.g. O:AAPL260724C00110000.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations include destructiveHint=true, but the description adds essential context that this action is narrowly scoped: 'it never touches a holding, so a stock the portfolio also owns stays exactly as recorded'. It also emphasizes user confirmation, providing significant behavioral guidance beyond the annotations.

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?

The description is two concise paragraphs: the first clearly states the action and its boundary, the second provides parameter addressing instructions. Every sentence serves a distinct purpose with no filler.

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?

The tool has no output schema, but for a removal action the description adequately covers what is removed, what is not affected, the confirmation requirement, and parameter addressing. It lacks information about return values or error cases (e.g., if the instrument is not watchlisted), but this does not hinder correct invocation.

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 descriptions already cover all three parameters (100% coverage). The description adds value by clarifying the mutual exclusivity of ticker vs optionContract and instructing the agent to use the format from GetMyPortfolio's Watching section, which reinforces parameter selection semantics.

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 clearly states 'Remove a stock or an option contract from one of the USER's portfolio watchlists', using the specific verb 'Remove' and resource 'watch entry'. It distinguishes from sibling tools like WatchInstrument and portfolio lot tools by explicitly limiting scope to watchlists.

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?

The description provides clear usage context: it must be used to remove a watch entry, and it instructs the agent to confirm with the user before acting. It also gives addressing guidelines (ticker vs OCC symbol as they appear in GetMyPortfolio). It doesn't explicitly list when not to use, but there are no ambiguous alternatives.

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

All equibles toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions that cross-reference related alternatives. A few near-duplicate names could cause misselection, notably SearchDocument versus SearchDocuments and GetCftcPositioning versus GetLatestCftcPositioning.

Naming Consistency5/5

Tool names consistently follow a VerbNoun camelCase pattern: Get for retrievals, Search for discovery, List/Read for document access, and Add/Close/Remove/Update/Watch/Create/Delete for portfolio mutations. Despite the large count, there is no mixing of naming conventions or unpredictable verb styles.

Tool Count1/5

108 tools is an extreme surface area, far beyond the 3-15 well-scoped range and well past the 25+ threshold. Even for a broad financial data platform, this creates a heavy selection burden and substantial context overhead for agents.

Completeness4/5

The server covers an unusually wide domain: prices, fundamentals, SEC filings, options, insider activity, 13F holdings, short interest, macro data, funds, IPOs, and full portfolio lifecycle management. Notable gaps remain, such as a basic company profile/ticker-resolution tool, dividend history, and analyst estimates, so it is not a perfect 5.

Resources