Skip to main content
Glama

Paraguay Dncp

by io.github.pipeworx-io
OverviewAdmin

Paraguay Get Record

paraguay_get_record
Read-onlyIdempotent

Get the full Paraguay procurement record for a process from the official DNCP Open Contracting (OCDS) API. Pass the numeric process id (e.g. 291566) or the ocid (e.g. "ocds-03ad3f-291566-1"). Returns the compiled OCDS release: ocid, title, buyer, contract value + currency (PYG), status, procurement method, key dates, tender items, and awards (suppliers + award amounts). Field values are in Spanish; keys are English.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProcess id (e.g. 291566) or full ocid (e.g. "ocds-03ad3f-291566-1").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "291566"
+  },
+  {
+    "id": "ocds-03ad3f-291566-1"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds value by specifying the API source, return format (OCDS release), field details (ocid, title, buyer, etc.), and language notes (Spanish values, English keys).

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?

Three well-structured sentences that front-load the purpose, then provide input and output details. No wasted words; each sentence earns its place.

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

Completeness5/5

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

For a simple tool with one parameter and no output schema, the description fully covers API source, input alternatives, output fields, and language nuances. Complete for the given complexity.

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% with examples. Description adds clarity by explicitly stating acceptable input formats and providing concrete examples, enhancing understanding beyond the schema.

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 uses the specific verb 'Get' and identifies the resource as 'full Paraguay procurement record'. It distinguishes from the sibling tool 'paraguay_search_tenders' by focusing on retrieving a single record by ID rather than searching.

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?

Provides clear input format guidance with examples (numeric ID or ocid). No explicit when-not or alternative usage, but the purpose is distinct enough that usage is implied from the sibling context.

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

All Paraguay Dncp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources