Skip to main content
Glama
Sign In

Pensiata - Bulgarian Pension Fund Analytics

by io.github.nvasilevv
OverviewDiscussionsAdmin

get_pension_legal_framework

Return the full text of Bulgarian pension legal documents.

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

Input Schema

NameRequiredDescriptionDefault
documentNoOptional filter – "ordinance_9", "ordinance_33", or "kso". If omitted, returns all available documents.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / document / description
      Added value: +"Optional filter – \"ordinance_9\", \"ordinance_33\", or \"kso\".\n      If omitted, returns all available documents."
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden of indicating behavior. It states 'Return', implying a read-only operation, but doesn't disclose potential nuances like access restrictions, error behavior, or that it returns all documents unless filtered. Overall, it's basic but not misleading.

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, front-loaded sentence with no redundant words. It efficiently communicates the core function without wasting tokens.

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?

Given the tool's low complexity (one optional parameter), an existing output schema, and clear schema coverage, the description plus schema is largely complete. It lacks a nod to related tools like search_pension_law, but that gap is already handled in the usage dimension.

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

Parameters3/5

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

The input schema fully describes the optional 'document' parameter, including allowed values and default behavior. The description adds no parameter-specific information beyond what the schema already covers, so the baseline score of 3 applies.

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 a specific verb ('Return') and resource ('full text of Bulgarian pension legal documents'), which distinguishes it from siblings like search_pension_law. It unambiguously states the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives. Although the sibling search_pension_law suggests a differing use case, the description does not mention it or offer any comparative context.

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 toolsInspect
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.

Resources