Skip to main content
Glama

DaallIndex — Saudi Government Awards Index

Government buyer summary

buyer_summary
Read-onlyIdempotent

Use this when the user asks how much a large Saudi government entity (a ministry, authority or directorate) awarded in contracts over the last 12 months, how that changed, or who its largest winners are. Takes the entity name in Arabic or English. Returns the award value and count, the change on the previous 12 months, the rank, the three largest winners by name, and the page url. Covers the 15 largest buyers only; not for a single tender. استعملها لسؤالٍ عن ترسيات جهة حكومية كبرى في 12 شهراً وتغيّرها وأبرز الفائزين بعقودها.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "buyer_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesاسم الجهة / buyer name in Arabic or English

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add scope and output context — which it does by disclosing the 15-largest-buyer coverage limit and enumerating the return fields. It does not say what happens when the requested entity falls outside those 15, leaving the failure mode undocumented.

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?

Well front-loaded: trigger, then input format, then return contents, then coverage limit. The full Arabic restatement is duplication for monolingual agents but serves a plausible bilingual audience and introduces no new ambiguity, so the length is defensible rather than wasteful.

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?

With no output schema, the description correctly carries the return contract (award value and count, prior-period change, rank, three largest winners, page url). Coverage is strong for a single-parameter tool; the only gap is the behavior when the entity is not among the 15 largest buyers.

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 schema already says the query is a buyer name in Arabic or English, so the description largely repeats it. The added value is modest — clarifying that the query should be a ministry, authority or directorate rather than a company or tender — which constrains acceptable values but does not go beyond that.

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?

States a specific verb and resource: award value/count, 12-month change and top winners for a large Saudi government entity. It also scopes the data set ('15 largest buyers only') and explicitly excludes the sibling use case ('not for a single tender'), so an agent can distinguish it from a tender-search tool.

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?

Opens with an explicit trigger ('Use this when the user asks how much a large Saudi government entity awarded...'), which covers the primary cases the tool serves. It adds one exclusion ('not for a single tender') but does not name which sibling to use instead, leaving that routing to 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