Skip to main content
Glama

start_refresh

Queue a durable background refresh of Polish public procurement notices and awards for a profile, returning a job_id immediately so you can poll status and search cached data while sources update.

Instructions

Enqueue a durable background refresh and return immediately with job_id.

    Fetch at most 120 publication days. include_results also fetches formal awards.
    Identical active requests reuse their job. The profile is snapshotted at submission.
    Poll refresh_status; search cached notices/results while completed sources become available.
    The local MCP server process must remain running for background work to continue.
    

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": {
      "profile": "<profile>"
    },
    "name": "start_refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
profileYes
source_namesNo
include_resultsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/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 well: it discloses asynchronous durable execution, immediate return with job_id, a 120-publication-day cap, idempotent reuse of identical active requests, profile snapshotting at submission, and the critical constraint that the MCP server process must stay running. It stops short of stating permission requirements or what happens to a job if the process dies mid-run.

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?

Front-loaded with the action and return value, then layered constraints in short sentences. Every line adds information, though the polling/caching sentence packs two distinct behaviors together and could be split for scanability.

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?

An output schema exists, so return values need no explanation, and the description covers async lifecycle, idempotency, and the process-lifetime caveat. The main gap is the undocumented source_names parameter and the absence of any note on what happens when the 120-day cap is exceeded.

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 five parameters, so the description must compensate. It explains include_results (also fetches formal awards) and profile (snapshotted at submission) and implies start/end via the 120-day cap, but source_names is never mentioned and no date format is given for start/end.

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 ("Enqueue a durable background refresh") plus the immediate return value (job_id), which distinguishes it from the polling sibling refresh_status named later in the text. An agent can tell this is the job-submission entry point rather than a status or resume call.

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?

Gives clear operational context: poll refresh_status after submitting, and search cached notices/results while sources complete. It does not explicitly contrast with resume_refresh or state when a new refresh is preferable to resuming an existing one, so the alternative-selection guidance is incomplete.

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