Skip to main content
Glama
l4b4r4b4b4
by l4b4r4b4b4

clone_portfolio

Create a copy of an existing portfolio to test different allocation strategies, with optional new weights.

Instructions

Clone an existing portfolio, optionally with new weights.

Creates a copy of a portfolio, useful for testing different allocation strategies on the same underlying assets.

Args: source_name: The name of the portfolio to clone. new_name: The name for the cloned portfolio. new_weights: Optional new weights. If None, uses source weights.

Returns: New portfolio information.

Example: ``` # Clone with same weights result = clone_portfolio( source_name="tech_stocks", new_name="tech_stocks_v2" )

# Clone with different weights
result = clone_portfolio(
    source_name="tech_stocks",
    new_name="tech_aggressive",
    new_weights={"GOOG": 0.6, "AMZN": 0.3, "AAPL": 0.1}
)
```

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_nameYes
new_nameYes
new_weightsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains that cloning creates a copy and optionally changes weights, and describes the return value as 'New portfolio information.' However, it omits details like permissions required, error conditions (e.g., source not found), or side effects on the source portfolio.

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 well-structured with a brief intro, Args list, Returns line, and a clear example. It is concise yet informative, with no unnecessary words.

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?

Given the presence of an output schema (context indicates 'Has output schema: true'), the description's brief mention of 'New portfolio information' is acceptable. However, it could mention constraints like source must exist or naming uniqueness, which would improve completeness for a tool with many siblings.

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

Parameters5/5

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

The schema has no descriptions for parameters (0% coverage), and the description fully explains each parameter in the Args section, including the optional new_weights with its default behavior. This adds significant value beyond the schema.

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 'Clone an existing portfolio, optionally with new weights.' It identifies the verb (clone) and resource (portfolio), and the context of testing allocation strategies distinguishes it from siblings like create_portfolio or update_portfolio_weights.

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 indicates the tool is for copying portfolios for testing different allocation strategies, and includes examples. However, it does not explicitly state when not to use it or compare it to alternatives like create_portfolio for new portfolios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/l4b4r4b4b4/portfolio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server