Skip to main content
Glama

DaallIndex — Saudi Government Awards Index

Index level

index_level
Read-onlyIdempotent

Use this when the user asks how much the Saudi government is awarding in contracts, overall or in one sector, or how that changed over a year. Returns the Daall Government Awards Index (DGI) or one sector index: the level, awards in the last 12 months in SAR bn, the change on a year earlier, and the page url. Not for a single company, buyer or tender. استعملها لسؤالٍ عن حجم الترسيات الحكومية السعودية كلّها أو في قطاع، وتغيّرها عن سنةٍ مضت.

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": "index_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoDGI (default) or a sector code: CAPG, CPS, SOFT, CONS, TRAN, UTIL, TELE, HLTH

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuine value beyond that by enumerating the returned fields — level, awards over the last 12 months in SAR bn, year-on-year change, and page url — which matters because there is no output schema. It does not discuss freshness/lag of the index data, so it stops short of a 5.

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 English portion is two tight sentences, front-loaded with the trigger condition and then the return payload. The Arabic sentence restates the same guidance verbatim, which is useful for matching Arabic-language user queries but is redundancy for an English-reading agent, keeping this just below a 5.

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?

This is a single-optional-parameter, read-only lookup with no output schema, and the description fully compensates by spelling out the return values and the default behavior. Between the description and the parameter docs, an agent has everything needed to call it correctly and interpret the result.

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 the sole parameter's description already lists DGI as the default plus all eight sector codes. The prose adds no further meaning about the code parameter (no guidance on choosing a sector), so the baseline 3 applies.

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 verb and resource — returning the Daall Government Awards Index level, either aggregate (DGI) or a single sector index — and explicitly scopes what it is not for (a single company, buyer or tender). Combined with the sector-code alternatives in the schema, an agent can distinguish this from siblings like buyer_summary or largest_awards.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete trigger condition ('when the user asks how much the Saudi government is awarding in contracts, overall or in one sector, or how that changed over a year') and an explicit exclusion ('Not for a single company, buyer or tender'). Both when-to-use and when-not-to-use are stated, so the agent needs no inference.

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