Skip to main content
Glama

منصة المناقصات — Saudi Government Tenders

بحث شامل / Search

search
Read-onlyIdempotent

Use this when you have a subject, an entity name, a company name or a month and need the matching records on منصة المناقصات (Saudi government tenders from Etimad, agencies, companies, monthly reports). Returns up to 20 results {id, title, url}, each id in the form tender:<reference_no>, agency:, company: or report:. Arabic keywords match more. ابحث في منصة المناقصات: منافسات وجهات وشركات وتقارير شهرية.

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كلمة البحث / search query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds real behavior: a hard cap of 20 results, the exact return shape {id, title, url}, and the ID grammar (tender:<reference_no>, agency:<id>, company:<id>, report:<YYYY-MM>). This is genuinely useful beyond the annotations, though nothing is said about empty results or pagination past 20.

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 trigger condition is front-loaded, followed by the return contract and the Arabic-keyword tip, so it reads in priority order. The trailing Arabic sentence largely restates the purpose already given in English, which is mild redundancy rather than harm.

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 shouldered the burden of describing the return payload and ID formats, and it did. The only small gap is behavior when more than 20 matches exist or when nothing matches, which an agent would need to know to avoid silent truncation.

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% with a single documented parameter, so the baseline is 3. The description earns a bump by telling the agent what a query may contain (subject, entity name, company name, or a YYYY-MM month) and that Arabic keywords match more effectively, which meaningfully shapes query construction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific capability: find matching records across tenders, agencies, companies and monthly reports on منصة المناقصات, and enumerates the four result ID forms, which implicitly scopes it wider than single-entity siblings. It never names an alternative (e.g. search_tenders or company_summary), so the differentiation is inferable rather than explicit.

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?

"Use this when you have a subject, an entity name, a company name or a month" gives concrete triggers tied to the query input, which is stronger than most search tools. It stops short of stating when not to use it or which sibling to prefer for a narrower lookup.

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