Skip to main content
Glama
Sign In
fin-data-mcp-server

fin-data-mcp-server

by CohenD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List World Bank data sources

worldbank_sources
Read-onlyIdempotent

List World Bank indicator data sources to obtain source IDs for filtering queries.

Instructions

List the data sources (databases) behind World Bank indicators, e.g. World Development Indicators, Doing Business. Use to discover a source id for filtering. Example: { perPage: 100 }

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

Input Schema

NameRequiredDescriptionDefault
perPageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds an example usage and mentions that the tool returns source IDs, which is useful but not extensive. It does not contradict annotations.

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 two sentences plus an example, all highly relevant. No superfluous words. The purpose is front-loaded.

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 simple listing tool with one optional parameter, the description is largely complete. It explains what the tool does and hints at usage. It does not describe the output format, but given the simplicity and the lack of output schema, this is acceptable.

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 schema has 0% description coverage for the single parameter 'perPage'. The description provides an example '{ perPage: 100 }' which implies pagination, but does not explicitly explain the parameter's purpose or behavior beyond that.

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 states the tool lists World Bank data sources, with specific examples (World Development Indicators, Doing Business). It distinguishes from sibling tools like 'worldbank_indicator' and 'worldbank_search_indicators' by focusing on source discovery.

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

Usage Guidelines4/5

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

The description explicitly states 'Use to discover a source id for filtering,' providing clear context for when to use this tool. However, it does not mention when not to use it or provide alternatives.

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

Deploy Server

Other Tools