Retrieve Strategic Portfolio Management portfolios from ServiceNow to identify active investments, filter by criteria, and control record volume for reporting or analysis.
List Strategic Portfolio Management portfolios (pm_portfolio). SPM is the evolution of PPM.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max records (default 20) | |
| query | No | Optional encoded query (e.g. active=true) | |
| fields | No | Comma-separated fields to return |
Changes observed during successful MCP inspections.
v4.17.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds nothing behavioral beyond that—no pagination behavior or return format—but the annotations lower the bar, so a 3 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the resource. The second sentence ('SPM is the evolution of PPM') is explanatory filler that doesn't earn its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only list tool with a complete schema and annotations, the description is minimally adequate. It lacks any return-format or pagination context, but none is strictly required given the annotations and full schema coverage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents limit, query, and fields. The description adds no parameter meaning beyond the schema. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'List Strategic Portfolio Management portfolios (pm_portfolio)', naming the exact table. It distinguishes itself from siblings like get_portfolio and list_programs, though the SPM/PPM acronym note is unhelpful filler that doesn't aid an agent in choosing among the many portfolio-related siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no mention of the alternative 'get_portfolio' for a single portfolio, and no exclusions. The agent gets no routing help despite many adjacent siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.