Skip to main content
Glama

PortfolioFit

List analysis portfolios

list_analysis_portfolios
Read-onlyIdempotent

List owner-scoped portfolios, analytics datasets, and profile readiness.

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_analysis_portfolios"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
portfoliosYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description usefully adds that results are 'owner-scoped' (implicitly the caller's owner, since there are no filtering parameters) and that profile readiness is bundled into the response. It does not mention pagination or result limits.

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?

One short, front-loaded sentence with no filler. It is efficient, though 'profile readiness' and the bundling of three resource types into one list are left unexplained, which slightly undercuts the brevity.

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?

With no input parameters, full annotation coverage, and an output schema that documents the return shape, the description does not need to explain values or pagination. It adequately conveys the tool's role for a simple, parameterless lister, though a hint on when to prefer it over list_analyses would make it complete.

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?

The schema has zero parameters with 100% description coverage, so there is nothing for the description to compensate for. Baseline for a no-parameter tool is 4; the description's note that scope is owner-determined is a small bonus.

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?

States a specific verb (List) and the resources returned (portfolios, analytics datasets, profile readiness), plus the scope qualifier 'owner-scoped'. It is clear what the tool does, but it does not distinguish itself from close siblings such as list_analyses or list_portfolio_series, which also enumerate related resources.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the nine siblings, several of which overlap (list_analyses, list_portfolio_series, review_portfolio_series_profile). No prerequisites, no exclusions, no routing guidance. The agent must infer usage entirely from the name.

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