Zephior Discovery

Read a public tender

get_public_tender

Read-onlyIdempotent

Read a published notice, source-backed facts, available requirements, original source, related notices and history. Missing information is explicitly unavailable. status is the effective status shown to visitors; recordedStatus is the reviewed status; sourceStatus is what the source portal states. sourceCheckedAt is when the original source was last read; modifiedAt is when this record last changed. stale true means a newer source version awaits republication; stale false does not mean that every portal publishing the procedure agrees. related lists notices that look like the same procedure elsewhere or an earlier or later version, with their deadlines: compare them, prefer the latest official change notice, and check the submission platform before relying on a deadline. history holds the latest revisions (historyTotal counts all; pass historyNextBefore as historyBefore for older ones).

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

Input Schema

Name	Required	Description	Default
`id`	Yes
`locale`	No		en
`historyLimit`	No
`historyBefore`	No	Continue history before this revision; pass historyNextBefore.

Output Schema

Name	Required	Default
`id`	Yes
`url`	Yes
`stale`	No
`title`	Yes
`locale`	Yes	en
`status`	Yes
`country`	No
`sources`	Yes
`summary`	Yes
`deadline`	Yes
`revision`	No
`modifiedAt`	Yes
`sourceStatus`	No
`originalSource`	Yes
`recordedStatus`	Yes
`sourceCheckedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026

addedInput schema / properties / historyBefore

Added value: +{
+  "description": "Continue history before this revision; pass historyNextBefore.",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / historyLimit

Added value: +{
+  "default": 30,
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

First observedOct 17, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real interpretive context beyond that: the three status fields are distinguished, stale true/false is qualified, and revisions are bounded by historyTotal/historyNextBefore.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core read action, and the status/staleness/history sentences each carry load, but the text is a dense semicolon-chain with multiple concerns interleaved and no separation between output semantics and guidance, making it heavier than necessary.

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 complex record with an output schema, the description supplies the interpretation an agent needs: status vs recordedStatus vs sourceStatus, staleness caveats, related-notice comparison, and history pagination. It stops short on error/not-found behavior and sibling routing, but is otherwise thorough.

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 low (25%) — only historyBefore is documented in the schema. The description partially compensates by explaining that historyNextBefore should be passed as historyBefore for older revisions, but locale and historyLimit remain unexplained in both places, leaving the gap only partly filled.

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 (Read) and resource (a published notice) and enumerates what is returned: source-backed facts, requirements, original source, related notices and history. The read-by-id nature separates it from siblings like search_public_tenders and list_public_tender_changes, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Offers actionable guidance on handling related notices ('compare them, prefer the latest official change notice, and check the submission platform before relying on a deadline') and pagination. However it never states when to choose this tool versus search_public_tenders or the list_* siblings, so routing guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Zephior Discovery tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?