Skip to main content
Glama
Sign In

Analyzera

by com.analyzera
OverviewDiscussionsAdmin

Delete a portfolio

delete_portfolio
DestructiveIdempotent

Delete a strategy or an account the client owns. Permanent.

What goes depends on the id. A strategy is removed. An account is removed with
its positions, history and attached documents, and any bank link is dropped.
Catalogue strategies, and the people or households above an account, are
refused. Returns a confirmation only; ``list_portfolios`` shows the updated list.

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": {
      "portfolio_id": "<portfolio_id>"
    },
    "name": "delete_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
portfolio_idYesA `strategy_id` from list_portfolios.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial context beyond annotations: deletion is permanent, accounts cascade to positions, history, documents, and bank links, while some object types are refused. It also states that only a confirmation is returned, supplementing the destructive and idempotent annotations with concrete consequences.

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?

Front-loads the core action and permanence warning, then explains id-dependent outcomes, refusals, and the return shape in compact form. Every sentence carries operational value without repetition.

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?

With rich annotations, full schema coverage, and no output schema, the description supplies the remaining needed context: permanence, cascading effects, refused cases, and how to verify the updated list. Nothing essential for correct invocation 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 coverage is 100%, but the description adds important meaning: the id may refer to either a strategy or an account, and the deletion behavior depends on which one it is. This supplements the schema's narrower wording that refers only to a strategy_id.

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: deleting a portfolio, clarified as either a strategy or an account. It distinguishes the affected object types and their outcomes, so an agent can tell it apart from siblings like delete_simulation or list_portfolios.

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?

Explains the conditions under which the tool applies, including what happens for strategy versus account ids, and notes that catalogue strategies and households above an account are refused. It points to list_portfolios for viewing the updated list, though it does not explicitly name a sibling alternative for deletion.

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

All Analyzera 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