Skip to main content
Glama

Moldova Tenders

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Moldova Search Tenders

moldova_search_tenders
Read-onlyIdempotent

Keyword search over recent Moldova (MTender) government procurement tenders. Scans the most recent tenders and returns those whose title, buyer, or CPV description contains the query (case-insensitive; Romanian text). Note: this is a client-side filter over recent tenders (MTender has no native full-text search), so it matches recent listings only. Returns shaped tenders like moldova_recent_tenders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scanNoHow many recent tenders to scan for matches (50–500). Default 200. Higher = more thorough but slower.
limitNoMax matches to return (1–50). Default 20.
queryYesKeyword to match against title / buyer / CPV description (e.g. "medicamente", "construc", "computer").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 20,
+    "query": "medicamente",
+    "scan": 200
+  },
+  {
+    "limit": 10,
+    "query": "construc"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context: it is a client-side filter (no native full-text search in MTender), case-insensitive, handles Romanian text, and explains the scan parameter trade-off. No contradictions with annotations.

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?

Two sentences: first states purpose with resource and action, second explains limitations and return shape. No extraneous information, front-loaded with key details. Every sentence adds value.

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 simple search tool with full schema and annotations, the description covers purpose, behavior (client-side filter), limitations (only recent), and parameter trade-offs. It references the return shape via another tool, which may require that tool's description for full clarity. Lacks error handling or empty result behavior, but is otherwise complete.

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 description coverage is 100%, with each parameter described. The description adds extra semantics: scan parameter explains that higher values are more thorough but slower, and query describes case-insensitive matching against title/buyer/CPV description. This goes beyond the schema's basic descriptions, justifying a 4.

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 states it performs a keyword search over recent Moldova MTender procurement tenders. It specifies the resource (tenders), action (search), and scope (recent, Moldova). It implicitly distinguishes from siblings like moldova_recent_tenders (which lists without search) and moldova_get_tender (single tender retrieval).

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?

The description explains that it is a client-side filter over recent tenders and matches only recent listings, implying a limitation. However, it does not explicitly state when to use this tool versus alternatives like moldova_recent_tenders or when not to use it. It only notes the return shape resembles moldova_recent_tenders, lacking clear separation of use cases.

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

All Moldova 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