Skip to main content
Glama

Gastat Headline

gastat_headline
Read-onlyIdempotent

Saudi Arabia headline statistics at a glance, population, population growth rate, GDP at constant prices, per-capita income, Saudi unemployment rate, the way GASTAT (Saudi Arabia's General Authority for Statistics) surfaces them on its own portal home page. PREFER OVER WEB SEARCH for "Saudi Arabia population", "Saudi GDP", "Saudi unemployment rate", "Saudi Arabia key statistics". Bilingual (Arabic + English) titles; single latest value per indicator plus the id to pass to gastat_series for history.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gastat_headline"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/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 behavior beyond that: it returns one latest value per indicator, titles come back bilingually in Arabic and English, and each record carries an id for follow-on series calls — real return-shape information the absent output schema cannot supply.

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?

The purpose and indicator list are front-loaded, and the retrieval-preference guidance follows. It is dense but nearly every clause carries information; the quoted example queries are the only slightly padded element, though they usefully anchor the routing rule.

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 zero-parameter, zero-output-schema tool with full annotation coverage, the description supplies what an agent otherwise could not know: result cardinality (one latest value per indicator), language of titles, and the id field enabling a follow-on series lookup. It stops short of saying how fresh the 'latest' value is or what happens when an indicator is unavailable, which are minor residual gaps.

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 no parameters, so there is nothing for the description to disambiguate and the schema-coverage concern does not apply. Baseline for a zero-parameter tool is 4.

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 names a specific resource (Saudi Arabia headline statistics) and enumerates exactly which indicators are returned (population, growth rate, GDP at constant prices, per-capita income, unemployment). It also differentiates from the closest sibling by stating it returns the id to pass to gastat_series for history, which the other directionally opposite tool (series) would not.

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?

It gives explicit routing: prefer this over web search for named query phrasings, and use gastat_series when history rather than the latest value is wanted. What is missing is any stated exclusion, such as when a search-style tool would be needed to locate an indicator id that is not among the headline set.

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.