thatmgmt-mcp

portfolio_exceptions

Retrieve a prioritized queue of portfolio health exceptions, including expiring certificates and commerce issues, to identify and address critical items.

Instructions

Prioritized operator exception queue derived from portfolio health (expiring certificates, commerce issues). Read-only, GET-only.

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": "portfolio_exceptions"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 18, 2026

TDQS

A4.3/5.0

Behavior4/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 explicitly states 'Read-only, GET-only' which covers safety and method. It also mentions 'Prioritized' indicating ordering behavior. It does not detail response format or error handling, but for a zero-parameter GET tool this is sufficient. No contradictions exist.

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 description is a single, dense sentence that front-loads the purpose and includes the key behavioral trait (read-only). Every word earns its place; no fluff or redundancy. It is exceptionally concise while remaining informative.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no parameters and no output schema, the description is complete. It explains what the tool returns (an exception queue), how it is derived, and that it is read-only. The agent has enough information to invoke it correctly without further elaboration.

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 tool has zero parameters, so there is nothing to document. The baseline for 0 params is 4. The description adds no param-specific information, but none is needed. The schema is empty and covered 100% by default, so this dimension is satisfied.

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?

The description clearly identifies the tool as a prioritized exception queue derived from portfolio health, and specifies the types of issues (expiring certificates, commerce issues). It also states it is read-only and GET-only, distinguishing it from potential write tools. This is a specific verb-like resource description with clear scope.

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?

The description implies the tool is for retrieving exceptions, but does not explicitly state when to use it versus siblings like portfolio_health or portfolio_renewal_risk. No when-not guidance or alternative routing is provided. The derivation from portfolio health gives some context, but the agent must infer the intended use case.

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

Deploy Server