Skip to main content
Glama

Kobo Terminal NGX

Treasury bill auctions

get_tbill_auctions
Read-onlyIdempotent

CBN Nigerian Treasury Bill auction results: tenor, amount offered, subscribed and allotted, subscription rate, stop rate and yields. Plan: Free+.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of auction rows, default 50, max 500. Example: 6

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered and the description need not repeat it. The description adds one useful non-schema fact, the 'Free+' plan requirement, but says nothing about data freshness, pagination beyond the limit param, or how auctions are ordered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence front-loads the source and resource before listing the returned fields, with zero wasted words. The trailing 'Plan: Free+' is slightly abrupt but still earns its place as an access constraint.

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 single-parameter read tool with rich annotations and no output schema, the description is close to sufficient: it effectively serves as a return-field listing. Missing only ordering/pagination behavior and freshness, which are minor 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% and the single limit parameter is documented there with default (50), max (500) and an example. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 a specific resource (CBN Nigerian Treasury Bill auction results) and enumerates the exact fields returned: tenor, offered/subscribed/allotted amounts, subscription rate, stop rate and yields. It is unambiguous about what the tool fetches, though it never explicitly distinguishes itself from near-neighbors like get_bonds or get_offers.

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?

There is no guidance on when to call this versus alternatives, no prerequisites, and no exclusions. The only contextual note is 'Plan: Free+', which conveys an entitlement tier rather than usage instructions.

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