Skip to main content
Glama

DaallIndex — Saudi Government Awards Index

Search DaallIndex

search
Read-onlyIdempotent

Use this when you have a company name, ticker, government entity, sector or topic and need the matching DaallIndex record. Searches listed companies, the largest government buyers, the indices and the research notes. Returns up to 10 results as {id, title, url}, with ids in the form company:, buyer:, index: or research:. ابحث باسم شركة أو رمزها أو جهة حكومية أو قطاع أو موضوع.

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

Input Schema

NameRequiredDescriptionDefault
queryYesكلمة أو اسم أو رمز / a name, ticker, index code or topic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 genuinely useful behavior beyond that: a hard cap of 10 results and the id format per entity type, which tells the agent what to expect back and how to route the id onward. It does not discuss ranking or what happens on zero matches, keeping it below 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?

Front-loaded with the trigger condition, then the coverage, then the return shape and id formats — a sensible order with no filler. The Arabic sentence duplicates the first sentence rather than adding information, which costs a little density but may be intentional for a bilingual audience.

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 one-parameter lookup with no output schema, the description supplies everything an agent needs: what corpora are searched, the result cap, the exact return fields, and the id conventions that connect this tool to the rest of the catalog. Nothing material is missing.

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 single parameter is already documented as 'a name, ticker, index code or topic'. The description largely restates that list, adding only 'government entity' and 'sector' as accepted query kinds. That is a marginal gain over structured data, 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?

States a specific verb (searches) plus the exact resources covered: listed companies, largest government buyers, indices, and research notes. The output shape and id prefixes (company:<ticker>, buyer:<id>, index:<code>, research:<id>) make it unambiguous that this is a resolution/lookup step rather than a data-retrieval tool like index_level or buyer_summary.

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 you have a company name, ticker, government entity, sector or topic and need the matching DaallIndex record.' That is a clear when-to-use condition. It stops short of naming when NOT to use it or pointing at the sibling tools (fetch, listed_company) once an id is in hand, so it falls short of a 5.

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