Skip to main content
Glama

Kobo Terminal NGX

Market news

get_market_news
Read-onlyIdempotent

Latest Nigerian business and capital-market headlines from BusinessDay, Nairametrics, Premium Times, SEC Nigeria and more. Plan: Starter+.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context beyond them: the publisher set and the Starter+ plan requirement, which tells the agent calls may fail on lower tiers. It does not describe result volume, refresh cadence, or failure behavior, keeping it at 3.

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 resource and scope (Nigerian business and capital-market headlines) before the source list, and the tier constraint placed last. No filler or redundant restatement of the title.

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

Completeness3/5

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

For a zero-parameter, no-output-schema tool with a full annotation set, the main remaining unknown is what actually comes back: number of headlines, fields per item, or whether it is a flat list. The description names sources but says nothing about return shape, leaving a gap an agent would notice when parsing results.

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

Parameters4/5

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

The tool takes zero parameters, which is the baseline-4 case; there is no parameter meaning the description needs to disambiguate. Nothing in the schema is left unexplained.

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?

States a specific verb+resource ('Latest ... headlines') and names the sourcing publishers (BusinessDay, Nairametrics, Premium Times, SEC Nigeria), which lets an agent see this is a news-feed tool rather than a numeric market-data tool like its siblings. It stops short of explicitly contrasting itself with any named sibling, so it lands at 4 rather than 5.

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 word 'Latest' hints at recency-oriented use, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling when the agent wants structured data instead of headlines. The one directive present ('Plan: Starter+') is an entitlement constraint, not usage guidance.

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