Skip to main content
Glama
Sign In
arpeio-mcp

arpeio-mcp

Official
by arpe-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

arpe_release_notes

Read-onlyIdempotent

Retrieve release-notes chunks for any Arpe.io product, optionally filtered by version, including ADBC driver "What's new" histories, to check changes and compatibility from the local docs cache.

Instructions

Return release-notes chunks for any Arpe.io product. Pass product to select which tool and optionally version to filter to a specific release. ADBC drivers are selected by load name (arpemssql, arpepgsql, arpeoracle, arpenz, arpeteradata) and return their "What's new" history. Read-only; queries the local docs cache.

Input Schema

NameRequiredDescriptionDefault
productYesWhich product's release notes to retrieve. ADBC drivers use their load name: arpemssql (ArpeMSSQL), arpepgsql (ArpePGSQL), arpeoracle (ArpeOracle), arpenz (ArpeNetezza), arpeteradata (ArpeTeradata).
versionNoOptional version string (e.g. '0.31', '0.4', '0.3.5'). Omit for the newest indexed version (the whole release history for an ADBC driver).

Output Schema

NameRequiredDescriptionDefault
countNoNumber of release-notes chunks returned.
chunksNo
statusYes'ok' when the call succeeded; 'error' when the parameters failed validation or execution failed.
productNo
versionNoRequested version, or null for the newest indexed.
docs_urlNoDocs to consult when release_notes_published is false.
release_notes_publishedNoPresent and false for products without release-notes pages (MigratorXpress).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.9
    • changedInput schema / properties / product / description
      Previous value: -"Which product's release notes to retrieve."New value: +"Which product's release notes to retrieve. ADBC drivers use their load name: arpemssql (ArpeMSSQL), arpepgsql (ArpePGSQL), arpeoracle (ArpeOracle), arpenz (ArpeNetezza), arpeteradata (ArpeTeradata)."
    • changedInput schema / properties / product / enum
      Previous value: -[
-  "fastbcp",
-  "fasttransfer",
-  "lakexpress",
-  "migratorxpress"
-]New value: +[
+  "fastbcp",
+  "fasttransfer",
+  "lakexpress",
+  "migratorxpress",
+  "arpemssql",
+  "arpepgsql",
+  "arpeoracle",
+  "arpenz",
+  "arpeteradata"
+]
    • changedInput schema / properties / version / description
      Previous value: -"Optional version string (e.g. '0.31', '0.4'). Omit for the newest indexed version."New value: +"Optional version string (e.g. '0.31', '0.4', '0.3.5'). Omit for the newest indexed version (the whole release history for an ADBC driver)."
    • addedOutput schema / properties / docs_url
      Added value: +{
+  "description": "Docs to consult when release_notes_published is false.",
+  "type": "string"
+}
    • addedOutput schema / properties / release_notes_published
      Added value: +{
+  "description": "Present and false for products without release-notes pages (MigratorXpress).",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.3.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "chunks": {
+      "items": {
+        "properties": {
+          "text": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of release-notes chunks returned.",
+      "type": "integer"
+    },
+    "product": {
+      "type": "string"
+    },
+    "status": {
+      "description": "'ok' when the call succeeded; 'error' when the parameters failed validation or execution failed.",
+      "enum": [
+        "ok",
+        "error"
+      ],
+      "type": "string"
+    },
+    "version": {
+      "description": "Requested version, or null for the newest indexed.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  3. First observedv0.3.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, so the safety profile is covered; the description adds meaningful context beyond that: it queries a local docs cache and ADBC drivers return their full 'What's new' history when no version is given. It restates 'Read-only' redundantly, which is the main thing keeping it from a 5.

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?

Short and front-loaded, with the core purpose in the first sentence and driver-specific behavior after. The sentence 'Pass `product` to select which tool' is imprecise wording that costs a bit of clarity but no padding is present.

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?

Output schema exists, so return-value description is unnecessary, and annotations cover safety. What remains is complete for an agent to call it correctly, with only the ambiguous 'select which tool' phrasing as a residual gap.

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 an enum on product and a documented version format, so the schema already carries the semantics. The description's ADBC load-name mapping and the 'whole history for a driver' behavior duplicate or lightly reinforce what the schema states, yielding the baseline 3.

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 and resource ('Return release-notes chunks for any Arpe.io product') and scopes the result set to a product/version. It is distinguishable from the *_info and search_docs siblings by scope, though it never names an alternative explicitly. The phrase 'select which tool' is slightly ambiguous but the intent (which product's release notes) is inferable.

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

Usage Guidelines3/5

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

Gives a clear input contract (pass product, optionally version; omit version for newest) but no when-to-use/when-not guidance relative to siblings such as search_docs, which could also surface release-note content. Usage is implied by the parameter narrative rather than stated.

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

Deploy Server

Other Tools