Skip to main content
Glama

Bullrun

by org.bull-run
OverviewDiscussionsAdmin

Create a position draft

create_position_draft

Use when the user asks what to BUY or ADD to an EXISTING portfolio — e.g. "what should I buy next", "suggest a stock or ETF for my portfolio", "what should I add", "recommend a position", "any ideas to round out my holdings". Generates REVIEWABLE suggested additions for one existing Bullrun portfolio. Requires OAuth with the write:drafts scope and a Bullrun Pro account. This is DRAFT-ONLY: the suggested position(s) are saved to the user's account and appear in the Bullrun Portfolio tab under Pending AI drafts, where the user reviews and accepts them into the target portfolio or discards them. It never changes live holdings by itself. To draft a whole new portfolio from scratch use create_portfolio_draft; to test whether a specific named ticker fits, use get_portfolio_analytics with candidateTicker. Pass instrumentUniverse for stocks only, ETFs only, or a mix. If it is unclear, first confirm which portfolio (use list_portfolios when the user has more than one) and how many ideas (a single best idea or a few) in ONE quick step; otherwise just build.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portfolioIdYesThe Bullrun portfolio id to propose additions for. Use list_portfolios first if unsure.
maxPositionsNoHow many suggested additions to save, 1-5. Use 1 for a single-position idea; default 3.
instrumentUniverseNoCandidate universe: stocks only, ETFs only, or a mix. Default mix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / instrumentUniverse
      Added value: +{
+  "description": "Candidate universe: stocks only, ETFs only, or a mix. Default mix.",
+  "enum": [
+    "stocks",
+    "etfs",
+    "mix"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate not read‑only and not destructive. The description adds that the tool is draft‑only and never changes live holdings, clarifying the write behavior. It also mentions required auth scope and account type. Slightly more detail on error handling would push it higher, but the current disclosure is strong.

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 description is front‑loaded with usage guidance and packs dense information. While it is longer than a single sentence, every sentence adds value. Could be slightly streamlined, but overall highly efficient.

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?

For a tool with 3 well‑documented parameters and no output schema, the description covers purpose, usage, behavior, parameter details, and sibling differentiation. It doesn't describe the response format, but given the tool's simplicity (draft creation), this is adequate.

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 covers 100% of parameters. Description adds value by explaining the instrumentUniverse parameter ('stocks only, ETFs only, or a mix'), advising to use list_portfolios for portfolioId, and noting default value for maxPositions (1 for single idea, default 3). This exceeds the baseline of 3 for high schema coverage.

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 the tool generates reviewable draft suggestions for adding positions to an existing portfolio, using specific verbs like 'generates REVIEWABLE suggested additions'. It explicitly distinguishes from siblings by naming create_portfolio_draft and get_portfolio_analytics.

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

Usage Guidelines5/5

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

The description specifies exactly when to use this tool (e.g., 'when the user asks what to BUY or ADD to an EXISTING portfolio' and gives example queries). It also tells when not to use it (for new portfolios or specific ticker checks) and provides prerequisites (OAuth scope, Bullrun Pro) and pre-invocation steps (confirm portfolio with list_portfolios).

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

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