Skip to main content
Glama

Model portfolio detail

rayana_ai_portfolio
Read-only

One model portfolio's full detail: holdings, overlay legs, event feed, NAV series, and windowed returns. Returns an error if the book's tier (e.g. an Elite-only book) is above the caller's own subscription tier.

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": {
      "slug": "<slug>"
    },
    "name": "rayana_ai_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe book's slug, as listed by rayana_ai_portfolios.

Output Schema

NameRequiredDescriptionDefault
navNo
asofNo
bookYes
slugYes
eventsNo
metricsNo
overlayNo
windowsNo
holdingsNo
delayed_toNo
factor_unwindNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"The book's slug, as listed by rayana_ai_portfolios."
  2. Changed2 schema fields changed
    • addedOutput schema / $defs / FactorUnwind
      Added value: +{
      +  "description": "Market-context banner: a recent crowded-winners unwind\n(forensics/momentum_crash_monitor.py) that touched this book's holdings.\n\nCarries only a COUNT of overlapping names, never the monitor's leg list.\nWhich names count as \"recent leaders\" is close to the momentum books' own\nselection lens, and the holdings themselves are already on the page.",
      +  "properties": {
      +    "date": {
      +      "title": "Date",
      +      "type": "string"
      +    },
      +    "flag": {
      +      "title": "Flag",
      +      "type": "string"
      +    },
      +    "held": {
      +      "title": "Held",
      +      "type": "integer"
      +    },
      +    "index": {
      +      "title": "Index",
      +      "type": "string"
      +    },
      +    "leg_size": {
      +      "title": "Leg Size",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "flag",
      +    "date",
      +    "index",
      +    "held",
      +    "leg_size"
      +  ],
      +  "title": "FactorUnwind",
      +  "type": "object"
      +}
    • addedOutput schema / properties / factor_unwind
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/FactorUnwind"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds genuinely new behavior in disclosing the subscription-tier gate and that an out-of-tier book produces an error. It does not discuss pagination or result-size limits, which is a minor residual gap.

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?

Two sentences, no filler: the content inventory comes first and the gating caveat second. Every clause carries information an agent would otherwise have to discover empirically.

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?

An output schema exists so return shape needn't be explained, annotations cover the read-only nature, and the one parameter is fully documented. What is missing is routing guidance versus nearby detail/summary siblings, which matters given the large sibling list.

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?

With 100% schema coverage on the single slug parameter (which already says it comes from rayana_ai_portfolios), the schema does the heavy lifting. The description adds only the 'book' terminology, clarifying that a book is a portfolio subject to tier rules — useful but marginal.

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+resource ('One model portfolio's full detail') and enumerates the payload it returns: holdings, overlay legs, event feed, NAV series, windowed returns. The singular 'one model portfolio' plus the slug parameter referencing rayana_ai_portfolios makes it clearly distinguishable from the list-level sibling.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers it should call this after rayana_ai_portfolios when it needs depth on a single book. There is no explicit when-to-use/when-not statement or named alternative, though the tier precondition is surfaced.

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