plaza-vea-mcp

by jeffreymonjacastro

Overview Schema Source Related Servers Discussions Admin

Python

Local

Consultar actualizacion del catalogo

get_catalog_refresh_status

Read-onlyIdempotent

Query the progress, outcome, and errors of a catalog refresh using its run ID to identify and resolve issues.

Instructions

Consulta progreso, resultado y errores de una actualizacion Scrapy.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_catalog_refresh_status"
  }
}

Input Schema

Name	Required	Description	Default
`run_id`	Yes

Output Schema

Name	Required	Description	Default
`pid`	Yes
`error`	Yes
`run_id`	Yes
`status`	Yes
`started_at`	Yes
`category_id`	Yes
`finished_at`	Yes
`products_processed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds specific data returned (progress, result, errors), which is useful but does not contradict the annotations. It stops short of describing error handling or edge cases.

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 a single, concise sentence that directly communicates the tool's purpose without unnecessary detail or redundancy.

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?

The description covers the basic function but lacks details on output structure, behavior for missing/invalid run_id, and its relationship to start_catalog_refresh is implied rather than explicit. Adequate for a simple status tool but with notable gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides run_id with length constraints but no description of its meaning. The tool description does not explain what run_id represents or how it should be obtained, leaving the parameter semantics ambiguous despite the self-explanatory name.

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 the tool's function: it queries progress, results, and errors of a Scrapy catalog refresh. This distinguishes it from sibling tools like start_catalog_refresh (which initiates a refresh) and the product search tools.

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

Usage Guidelines2/5

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

The description lacks explicit guidance on when to use this tool, such as 'after starting a refresh' or 'to check if a refresh completed'. It only states the function without usage context or comparison to alternatives.

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

Deploy Server