Skip to main content
Glama

PortfolioFit

List portfolio series

list_portfolio_series
Read-onlyIdempotent

Discover owner-scoped immutable series profiles and their exact dataset versions. This returns metadata and coverage only, never dataset rows.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_portfolio_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
statusesNo
page_sizeNo
portfolio_idNo

Output Schema

NameRequiredDescriptionDefault
seriesYes
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds meaningful context beyond that: results are owner-scoped, profiles are immutable, and the response contains metadata/coverage but never dataset rows. Pagination and result-count behavior are not disclosed, but the row-exclusion caveat is genuinely useful.

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 tight sentences, front-loaded with the discovery action and immediately followed by the key exclusion constraint. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-value detail is rightly omitted. However, with four undocumented parameters at 0% schema coverage, the description leaves filtering and pagination behavior unexplained, which is a real gap for a list tool an agent must call correctly.

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

Parameters2/5

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

Schema description coverage is 0% for all four parameters (cursor, statuses, page_size, portfolio_id), so the description must carry the burden and it does not. It mentions no filtering, pagination, or scope behavior tied to any parameter. 'Owner-scoped' loosely gestures at portfolio_id but never explains its role or the status filters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (portfolio series profiles) and clarifies scope with 'owner-scoped immutable series profiles and their exact dataset versions'. It distinguishes itself from row-oriented siblings via 'never dataset rows', but does not explicitly differentiate from the closer list/review siblings like list_analyses or review_portfolio_series_profile.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternatives named. Usage is only implied: the 'metadata and coverage only, never dataset rows' clause hints it is a discovery tool rather than a row-fetch or review tool. Nothing routes the agent between this and review_portfolio_series_profile.

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