Skip to main content
Glama

DaallIndex — Saudi Government Awards Index

Largest recent awards

largest_awards
Read-onlyIdempotent

Use this when the user asks about the biggest recent Saudi government contract awards. Returns the three largest awards of the last 60 days: winner, buyer, value in SAR m and date. Takes no arguments and does not filter by company, buyer or sector. استعملها لسؤالٍ عن أكبر الترسيات الحكومية السعودية الأخيرة.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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, so the safety profile is covered. The description adds real behavioral detail beyond them: a fixed 60-day window, a hard result cap of three, the exact returned fields, and that it accepts no arguments and performs no filtering — which prevents an agent from assuming it can be narrowed.

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 text is front-loaded and dense: trigger, output shape, and scope limits in three short clauses. The Arabic sentence repeats the same content for a second audience, which is defensible but does extend the length without adding new information for an English-reading agent.

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?

For a zero-parameter, fixed-window tool with no output schema, the description supplies everything needed: the trigger condition, the time window, the result count, the returned fields, and the absence of filtering. An agent can decide whether to call it and predict the response shape from the text alone.

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?

With zero parameters the baseline is 4, and the description reinforces the empty-schema fact by stating 'takes no arguments,' which guards against an agent trying to pass a filter. Nothing further is needed at this parameter count.

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 concrete resource and scope — 'the three largest awards of the last 60 days' — and lists exactly what each result contains (winner, buyer, value in SAR m, date). It also rules out the filtering siblings do ('does not filter by company, buyer or sector'), so an agent can tell it apart from 'search' or 'buyer_summary' without opening any schema.

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 an explicit trigger ('when the user asks about the biggest recent Saudi government contract awards') and an explicit non-capability (no company/buyer/sector filtering), which implicitly routes filtered queries to the search-style siblings. It stops short of naming an alternative tool, so the agent must infer where to go for filtered or older queries.

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