Skip to main content
Glama

Kobo Terminal NGX

FX rates (NGN)

get_fx_rates
Read-onlyIdempotent

Naira exchange rates against USD, EUR, GBP, CAD, AUD, CNY, JPY, GHS, ZAR and AED. Plan: Professional+.

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

Input Schema

NameRequiredDescriptionDefault
symbolsNoComma-separated currency codes. Example: USD,GBP,EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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=false, so the safety profile is fully covered structurally. The description adds the access-tier constraint (Professional+), which is genuinely useful context not present in the annotations. It stops short of describing whether rates are real-time or end-of-day, which matters for a market-data tool.

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?

Two short sentences, front-loaded with the currency scope and ending with the plan caveat. Nothing is redundant and every clause carries information.

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 one-parameter, read-only lookup with full annotation coverage, the description supplies scope, currency universe and the plan gate. With no output schema, the return shape is only implied (rates per currency), which is a minor gap for a simple numeric lookup. Nearly complete for this complexity level.

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 description coverage is 100%, so the single symbols parameter is already fully documented with an example. The description's currency list hints at the default universe returned when symbols is omitted, but never states that behavior explicitly. Baseline 3 is appropriate when the schema already carries the parameter detail.

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 names the resource precisely: NGN exchange rates against a specific enumerated list of ten currencies. It is instantly distinguishable from sibling tools such as get_bonds or get_price_history. It lacks an explicit verb ('get'/'list'), but the noun phrase is specific enough that an agent knows exactly what it returns.

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 implied by the description (fetch NGN FX rates), and the 'Plan: Professional+' note usefully flags a subscription prerequisite before the agent attempts a call. However, there is no explicit when-to-use versus alternative, no mention of whether quotes are live or reference rates, and no guidance on when to omit the symbols parameter.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources