Skip to main content
Glama

tenders

by tw.tobid
OverviewDiscussionsAdmin

framework_contracts

共同供應契約：機關不用另外招標、可直接下單的品項與廠商。 mode="awards"（預設）：共契決標公告，一案一列，附品項（名稱、決標金額）與得標廠商；q 逐詞比對案名、機關、品項、廠商， vendor 給廠商正式全名，year 西元或民國年。 mode="catalog"：現行共契品項目錄（工程會開放資料，限具環保標章品項），一列一個品項×廠牌型號×立約商，涵蓋台銀集中採購的 電腦主機、螢幕、印表機、耗材、投影機、冷氣、影印機租賃等 18 個契約與各醫院衛材藥品（附決標單價）；筆電、軟體等不在內。 q 比對品項、型號、廠商、分類，vendor 可給統編。 mode="series"：契約系列——同一機關同一系列（如台銀「電腦設備用品」）的歷期歸在一起，回每系列期數、慣例決標月份、 最近一期金額與得標家數、下一期預估年月（依歷期間隔推算）；q 比對系列名／機關，vendor 不適用。 mode="series_detail"：某一系列的每期明細與立約商進出（新進／退出／連續在榜），q 給系列名、unit_id 給機關代碼（從 series 結果取）。 mode="vendor"：一家廠商的共契版圖——歷年共契決標、現行目錄裡的品項數／分類／廠牌、同品項的競爭者；vendor 給正式全名。 問「某型號／某類商品共契由哪些廠商供應」用 catalog；問「哪家廠商拿過共契、金額多少」用 awards； 問「這個共契多久招一次、下一輪大概什麼時候、誰進誰出」用 series／series_detail。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo
modeNoawards
pageNo
yearNo
limitNo
vendorNo
unit_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mode
      Added value: +{
+  "default": "awards",
+  "title": "Mode",
+  "type": "string"
+}
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: it discloses data source (工程會開放資料), scope limitation (限具環保標章品項), exclusions, per-mode output contents, matching logic for q, and how parameters like vendor and unit_id are interpreted in each mode.

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

Conciseness5/5

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

The description is long, but the tool has five distinct modes and no schema/description coverage. Every block earns its place: the opening sentence frames the domain, each mode block adds required behavior, and the closing routing sentence converts user intent into mode selection without padding.

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?

Given the tool's complexity, the absence of annotations, a 0%-coverage schema, and no output schema, the description is remarkably complete. An agent can determine which mode to call, which parameters to supply, what data to expect back, and what is deliberately out of scope.

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 0%, so the description must compensate. It richly explains mode, q, vendor, year, and unit_id semantics. The only gap is page and limit, which appear only as numeric defaults with no explanation of pagination behavior or limits.

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?

The description clearly defines the resource: Taiwan's 共同供應契約 (framework contracts) for direct government ordering without separate tendering. It further breaks the tool into five explicit modes, each with a distinct resource scope (award announcements, current catalog, contract series, series details, vendor landscape), so there is no practical ambiguity with sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The final routing paragraph gives explicit when-to-use instructions: '問某型號／某類商品共契由哪些廠商供應' → catalog, '哪家廠商拿過共契、金額多少' → awards, and duration/entrant questions → series/series_detail. It also states exclusions such as laptops/software not in catalog and vendor being inapplicable in series mode.

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

All tenders toolsInspect
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