Skip to main content
Glama
Portfolio MCP Server

Portfolio MCP Server

get_data_info

Read-onlyIdempotent

Retrieve portfolio data freshness: its date, source (live repository or bundled package copy), project count, and package version. Use it to verify how current the portfolio is.

Instructions

Say how current the portfolio data is: its date, whether it came from the live repository or the copy bundled with the installed package, how many projects it holds, and the package version.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.6/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 openWorldHint=false, so the safety profile is covered by structured data. The description adds useful behavioral context in naming the two possible data sources (live repository vs the copy bundled with the installed package), which tells the agent results may be stale. It says nothing about cost, caching, or any side effects beyond the annotations.

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?

A single sentence with a front-loaded purpose and a compact enumeration of the four facts returned; no filler. The phrasing is slightly convoluted ("Say how current...") but it wastes no words and requires no restructuring.

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?

For a parameterless read-only metadata tool with full annotation coverage and an output schema, the description covers everything needed to decide to call it. Slight redundancy in enumerating return fields the output schema already documents keeps it from a 5.

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 the baseline is 4; there is nothing for the description to disambiguate. It correctly avoids inventing arguments and simply describes the report content.

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 uses a specific verb ("Say how current") tied to a concrete resource (portfolio data metadata) and enumerates the exact facts reported: date, provenance (live repository vs bundled copy), project count, and package version. That is enough to separate it from the sibling tools that return project content, though it never explicitly contrasts itself with them.

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?

Usage is only implied: an agent can infer this is the tool for checking data freshness/provenance before trusting other results. There is no explicit when-to-use statement, no exclusion of alternatives, and no guidance on when freshness checking matters versus being unnecessary.

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