Skip to main content
Glama

search_results

Search stored procurement awards by buyer, CPV codes, keywords, or region, and optionally refresh notices for a saved profile.

Instructions

Search stored awards by buyer, CPV, keywords and buyer region.

Optional refresh fetches contract and result notices for a known profile, at most 120 days. A named profile filters cached awards as well as optional refresh. Explicit CPV, exclusion, keyword and region arguments override that profile's corresponding fields, including empty lists. Contract notice types and submission deadline rules do not constrain historical awards. The result lists one latest award per procedure and lot, with its source notice. coverage describes acquisition windows and scopes per source, independently of result counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpvNo
endNo
buyerNo
limitNo
startNo
offsetNo
profileNo
refreshNo
regionsNo
exclude_cpvNo
keywords_anyNo
exclude_keywordsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses useful behavior: refresh triggers network fetching of contract and result notices, deduplicates to one latest award per procedure and lot, and ignores contract-notice-type and deadline rules for historical awards. However, it says nothing about refresh cost/latency, failure modes, or whether refresh mutates stored cached state — gaps that matter for a tool with a side-effecting-sounding flag.

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?

The core capability is front-loaded, and the remaining sentences are dense with rules rather than filler. It is slightly long and uses run-on declarative sentences that would read better as a short list, but no sentence is disposable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is an output schema, so return-value explanation (coverage, source notice) is reasonably delegated, and the description names those fields. For a 12-parameter, unannotated search tool, though, the description should also cover pagination and date-range parameters and the cost profile of refresh; those omissions leave real decision gaps.

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 0% across 12 parameters, yet the description only explains the semantics of the filter trio, profile, refresh, and exclusion lists (including the empty-list override trap). It never defines start/end date formats, limit/offset pagination, or the difference between keywords_any and exclude_keywords, leaving roughly half the parameters undocumented anywhere.

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?

The first line gives a specific verb and resource ('Search stored awards') plus the facets it matches on (buyer, CPV, keywords, buyer region). It is clear what the tool does, but it never distinguishes itself from siblings such as search_notices or procedure_results, so an agent must infer that this one searches awards rather than notices.

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?

It clearly explains the two usage modes: cached search versus optional refresh of a known profile (capped at 120 days), and states the precedence rule that explicit CPV/exclusion/keyword/region arguments override the profile's fields, including empty lists. What is missing is explicit when-not guidance or a named alternative for the notice-side search.

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