Skip to main content
Glama
simap MCP Server

simap MCP Server

by Digilac

Get Publication History

get_publication_history
Read-onlyIdempotent

Retrieve a project's publication history, including corrections and awards, to review changes and track tender updates by publication ID.

Instructions

Get the publication history for a project (corrections, awards, etc.)

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": {
      "publicationId": "<publicationId>"
    },
    "name": "get_publication_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
lotIdNoLot ID (optional, to filter by lot)
publicationIdYesCurrent publication ID (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.3.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description contributes the useful detail that results include events like corrections and awards, but says nothing about ordering, pagination, or how much history is returned.

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?

A single front-loaded sentence with no filler; the resource and scope land immediately. Its brevity borders on under-specification, with 'etc.' leaving the scope of returned history open.

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?

This is a simple two-parameter read tool with full schema coverage and rich annotations, so little is required. However, with no output schema, the description makes no attempt to characterize the shape or size of the returned history beyond naming example event types.

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 coverage is 100%, with both publicationId and the optional lotId filter fully documented in the schema. The description adds no parameter-level meaning, and the phrase 'for a project' does not clarify the publicationId/lotId relationship, so it sits at the baseline.

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?

States a specific verb ('Get') and resource ('publication history'), scoped to a single project, and gives concrete content examples ('corrections, awards, etc.'). It does not explicitly distinguish itself from siblings like get_tender_details or search_tenders, keeping it at 4 rather than 5.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives such as get_tender_details or the search_* tools. The use case is only inferable from the name and resource.

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