Skip to main content
Glama

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

جلب نتيجة / Fetch

fetch
Read-onlyIdempotent

Use this when you have one id and need its full record. Takes tender:<reference_no>, agency:, company: or report: 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المعرّف / id such as tender:<reference_no>

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add context, which it does by disclosing the exact return shape {id, title, text, url, metadata}. It does not say what happens for an unknown or malformed id, which is the main remaining gap for a single-record lookup.

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 condition, followed by accepted id forms and the return shape — three short, purposeful sentences. The trailing Arabic sentence largely restates the preceding sentence (adding only the page-link detail), so it is mildly redundant but not wasteful.

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, annotation-covered read tool with no output schema, the description supplies both the accepted id grammar and the return field list, which is most of what an agent needs. Only failure behavior for unknown ids is left uncovered.

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 schema shows only one example form (tender:<reference_no>); the description adds material meaning by listing the other three accepted prefixes and the report month format. That genuinely compensates beyond the schema's single example, though it does not state what happens if a prefix is omitted.

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?

Names a concrete verb-and-resource pair: fetch the full record for one id, and enumerates the four id namespaces it accepts (tender:<reference_no>, agency:<id>, company:<id>, report:<YYYY-MM>). This clearly separates it from multi-result siblings like search, though no sibling is named explicitly.

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 one id and need its full record" gives an explicit trigger condition that implicitly contrasts with the search tools for multi-item lookups. It stops short of stating when-not-to-use or naming a specific alternative, so it is clear context rather than full routing guidance.

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