Skip to main content
Glama

portfolio_exposure

Read-only

Summarizes AI portfolio exposure by department and risk tier, flags prohibited systems and pending assessments, and quantifies evidence gaps for governance review.

Instructions

Management summary: use cases per tier and department, prohibited systems in use, assessments awaiting review, and the size of the evidence gap.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description need not restate it. It does add value by disclosing the contents of the report, which tells the agent this is an aggregated snapshot rather than raw records. It stops short of stating scope (organization-wide vs. caller's own portfolio), data freshness, or whether values are counts or full lists.

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?

A single front-loaded sentence that first labels the output type and then lists its contents. Every clause corresponds to actual returned data, with no filler or hedging.

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 parameters, an output schema to describe the return shape, and read-only annotations, the description only needs to say what the summary covers — which it does comprehensively. The one meaningful gap is the missing scoping statement (whose portfolio, and over what period), which matters for a reporting tool.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter information is needed or missing.

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 names a specific deliverable — a management-level rollup — and enumerates the four data categories it reports: use cases per tier and department, prohibited systems, assessments awaiting review, and evidence-gap size. That is concrete enough to distinguish it from single-record tools like get_application, though the opening noun phrase 'Management summary' is somewhat label-like rather than a verb+resource statement.

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 'Management summary' framing implies a portfolio-overview use case rather than a per-item lookup, which is a reasonable implicit signal. However, no explicit when-to-use or when-not-to-use guidance is given, and the definition never says how this differs from the sibling evidence_gaps tool despite covering 'the size of the evidence gap'.

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