Pensiata - Bulgarian Pension Fund Analytics

get_bulgarian_pension_fund_managers

Alias for list_managers with explicit Bulgarian pension context for agent discovery.

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

Input Schema

Name	Required	Description	Default
`scheme_code`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedMar 5, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the burden. It only states it is an alias, providing no detail on side effects, permissions, data scope, or behavior. Since the alias target's behavior isn't described here, the agent gets minimal transparency.

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, concise sentence that directly states the tool's nature as an alias. It is front-loaded and contains no unnecessary words, earning its place.

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?

As a simple alias with one optional parameter and an output schema, the description is minimal but reasonably complete for an alias note. However, it assumes knowledge of `list_managers` and does not explain the parameter or any behavior beyond the alias relationship, leaving gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not mention the `scheme_code` parameter, and the schema itself has no descriptions (0% coverage). The enum values (upf, ppf, dpf) and default null offer some semantic clues, but the description adds no meaning, leaving the parameter's purpose ambiguous.

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 identifies the tool as an alias for `list_managers` with a Bulgarian pension context, making the resource and scope clear. It distinguishes from sibling tools by explicitly targeting Bulgarian pension fund managers, though it lacks a direct verb like 'lists'.

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 phrase 'with explicit Bulgarian pension context for agent discovery' implies use for Bulgarian pension scenarios, but it does not explicitly say when to use this over the generic `list_managers` or other alternatives. No clear exclusions or alternative suggestions are given.

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

All Pensiata - Bulgarian Pension Fund Analytics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.