Skip to main content
Glama
Sign In
customplanview MCP server

customplanview MCP server

by rushireddy143
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

planview_get_portfolio

Retrieve a single Planview portfolio using its unique identifier. Use it to fetch portfolio details for reporting, analysis, or planning.

Instructions

Get one portfolio by its Planview identifier.

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": {
      "portfolioId": "<portfolioId>"
    },
    "name": "planview_get_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
portfolioIdYesPlanview portfolio identifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only lookup but says nothing about permissions, error behavior when the ID is missing or invalid, rate limits, or what is returned.

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 definition is a single, front-loaded sentence with no filler. Every word contributes to identifying the operation and its lookup key.

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?

For a one-parameter read operation with full schema coverage, the description is minimally sufficient for invocation. However, with no output schema and no annotations, it leaves the return shape and failure behavior unspecified.

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?

Schema description coverage is 100%, so the single portfolioId parameter is already fully documented in the schema. The description restates the identifier requirement but adds no format, syntax, or constraint details beyond what the schema provides, making the baseline 3 appropriate.

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?

The description states a specific verb ('Get') and resource ('one portfolio') with the lookup key ('by its Planview identifier'). This implicitly distinguishes it from the list/search siblings, but it never names them or explicitly contrasts the operations.

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 guidance on when to use this tool versus planview_list_portfolios or planview_search_portfolios. The only implied context is that a Planview identifier must already be known, but no prerequisites or exclusions are stated.

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

Deploy Server

Other Tools