Skip to main content
Glama

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

تفاصيل منافسة / Tender details

get_tender
Read-onlyIdempotent

Use this when you have an Etimad reference number and need that one tender: agency, activity, deadlines, booklet price, winners and awarded values, the Etimad link and the page url. Takes the reference number as written. Not for finding tenders by subject. تفاصيل منافسةٍ واحدة برقمها المرجعي: الجهة والنشاط والمواعيد وقيمة الكراسة والفائزون.

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": {
      "reference_no": "<reference_no>"
    },
    "name": "get_tender"
  }
}

Input Schema

NameRequiredDescriptionDefault
reference_noYesالرقم المرجعي / Etimad reference number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 the safety profile is fully covered structurally. The description adds genuine context by listing the payload contents (winners, awarded values, booklet price) and the input-format caveat 'Takes the reference number as written'. It says nothing about failure behavior when a reference is unknown, which is the main remaining gap.

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 payload, then the exclusion — a sensible order with no filler. The Arabic sentence repeats the same content rather than adding any, a deliberate bilingual choice but still mild redundancy for an agent parsing English.

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 single-parameter read-only lookup with full annotation coverage, this is complete: trigger, input format, returned fields, and the boundary against subject search are all present. With no output schema, the inline field enumeration does the necessary work of describing the return.

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% and the single parameter already has a bilingual description, so the baseline is 3. The description earns an extra point with 'Takes the reference number as written', which tells the agent not to normalize, pad, or reformat the reference — meaning the schema does not convey.

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?

Names a specific verb+resource ('get_tender' / 'need that one tender') and enumerates the returned fields: agency, activity, deadlines, booklet price, winners and awarded values, Etimad link and page url. The explicit exclusion 'Not for finding tenders by subject' cleanly separates it from the search-family siblings.

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?

Gives a clear selection condition ('when you have an Etimad reference number and need that one tender') plus a negative rule ('Not for finding tenders by subject'). It stops short of naming the alternative tool (e.g., search_tenders) that should be used instead, leaving the agent to infer the redirect.

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