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

fin-data-mcp-server

by CohenD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

World Bank country metadata

worldbank_country
Read-onlyIdempotent

Retrieve detailed metadata for a country or region: ISO codes, region, income level, lending type, capital, and geographic coordinates.

Instructions

Metadata for a single country/region: ISO codes, region, income level, lending type, capital, coordinates. Example: { code: "US" }

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "worldbank_country"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesISO country/region code, e.g. US, CN, EUU

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds value by listing the metadata fields returned, but does not provide further behavioral context like rate limits.

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 sentence with an example, containing no unnecessary words and is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter tool with rich annotations, the description provides sufficient detail about the output fields and example usage.

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?

Schema coverage is 100% and adequately describes the 'code' parameter. The description adds an example but no extra meaning beyond the schema.

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 it provides metadata for a single country/region, listing specific fields (ISO codes, region, income level, etc.), and distinguishes it from sibling tools like worldbank_list_countries.

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 implicitly indicates when to use this tool (for a single country) versus siblings (worldbank_list_countries for all countries), but lacks explicit when-not or alternative guidance.

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