Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scan": 200,
      "limit": 20,
      "query": "medicamente"
    },
    "name": "moldova_search_tenders"
  }
}

Input 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. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max matches to return (1–50). Default 20."New value: +"Max matches to return (1-50). Default 20."
    • changedInput schema / properties / scan / description
      Previous value: -"How many recent tenders to scan for matches (50–500). Default 200. Higher = more thorough but slower."New value: +"How many recent tenders to scan for matches (50-500). Default 200. Higher = more thorough but slower."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "limit": 20,
      +    "query": "medicamente",
      +    "scan": 200
      +  },
      +  {
      +    "limit": 10,
      +    "query": "construc"
      +  }
      +]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the description's job is the extra context. It discloses the key behavioral fact that this is a client-side filter because MTender has no native full-text search, which means match completeness depends on the scan window. That is genuinely useful for interpreting results, though it could say more about how matches are ordered or truncated by limit.

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?

Three sentences, front-loaded with the core purpose and follow-up caveats in descending order of importance. The 'Note:' framing is slightly awkward but earns its place by flagging the coverage limitation.

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 three-parameter read tool with no output schema, the description supplies the essentials: matching fields, case and language behavior, recency caveat, and a pointer to moldova_recent_tenders for the result shape. Ordering of returned matches is the only notable omission.

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%, so parameter meaning is largely carried by the schema and the baseline is 3. The description adds real value beyond it, namely that matching is case-insensitive and targets Romanian text, and it implicitly explains why scan exists (no server-side search).

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?

States a specific verb and resource: keyword search over recent Moldova (MTender) government procurement tenders. It also distinguishes itself from the plain-listing sibling by declaring itself a filtered search, and points at moldova_recent_tenders for the return shape.

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?

The description clearly frames when this tool applies: keyword matching across title, buyer, or CPV description. It also sets an explicit boundary on recency coverage. It stops short of naming a concrete alternative for non-keyword or historical needs, so it falls just short of a 5.

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.