Skip to main content
Glama

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

المنافسات المفتوحة / Open tenders

open_tenders
Read-onlyIdempotent

Use this when the user wants tenders that are open for bidding now, for example in an activity or a region, or closing within a number of days. Takes optional activity, region and closing-within-days filters and no keyword. Returns up to 20 tenders, closing soonest first, with page urls. المنافسات المفتوحة للتقديم الآن، الأقرب إغلاقاً أوّلاً، بفلتر النشاط والمنطقة ومدة الإغلاق.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
regionNoالمنطقة / region
activityNoالنشاط / activity
closing_within_daysNoيُغلق خلال N يوماً / closes within N days

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that: result cap of 20, 'closing soonest first' ordering, and that each result includes page URLs. It does not mention pagination or what happens when more than 20 matches exist.

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 usage trigger, followed by filters and then return behavior in three tight sentences. The trailing Arabic sentence largely duplicates the English content, which is defensible for a bilingual title but adds length without new information.

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 four optional params and no output schema, the description does what is needed: it explains the filters it accepts, the result cap, sort order, and that URLs are included. Minor gaps remain around the limit parameter and behavior past 20 results, but nothing blocks a correct call.

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 description coverage is 75%, so region, activity, and closing_within_days are already documented in the schema and the description only restates them. The one undocumented parameter, limit, is not explained in the description at all (its 20 cap is only alluded to via 'up to 20 tenders'). Baseline 3 is appropriate.

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 verb and resource: returns tenders that are 'open for bidding now', optionally filtered by activity, region, or closing window. The clause 'and no keyword' signals how it differs from a keyword search sibling, but the sibling is never named, so differentiation is implied 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?

The opening 'Use this when the user wants tenders that are open for bidding now...' gives a clear trigger condition plus example framings (activity, region, closing within N days). It also rules out keyword-style queries ('no keyword'), which implicitly routes keyword searches elsewhere. No explicit named alternative or when-not statement beyond that.

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