Skip to main content
Glama

DaallIndex — Saudi Government Awards Index

Fetch a DaallIndex record

fetch
Read-onlyIdempotent

Use this when you have an id from search results and need the full record. Takes one id (company:, buyer:, index: or research:) and returns {id, title, text, url, metadata}. يجلب السجلّ الكامل لمعرّفٍ واحد من نتائج البحث.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesمعرّف من نتائج البحث / an id from search results

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 read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds value by spelling out the accepted id namespaces and the returned shape ({id, title, text, url, metadata}), which no output schema provides.

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 when-to-use condition, followed by input format and return shape in two compact sentences. The Arabic restatement duplicates the English content rather than adding information, which costs some efficiency.

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 single-parameter read tool with full annotations and no output schema, the description covers when to call it, how to format the id, and what comes back. Only minor gaps remain, such as behavior on an invalid or stale id.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful detail beyond the schema's generic 'an id from search results': it enumerates the four id prefixes (company:, buyer:, index:, research:), which directly affects how the agent should construct the parameter.

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: retrieve the full record for one id obtained from search results. This distinguishes it from the search/list siblings, which return result sets rather than single full records.

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?

Explicitly says to use it when you already have an id from search results and need the full record, which implies searching first. It does not name an alternative tool or state when not to use it, so it falls short of the top mark.

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