get_migration_notesGet upgrade notes between RevoGrid versions.
| Name | Required | Description | Default |
|---|---|---|---|
| framework | No | ||
| toVersion | Yes | ||
| fromVersion | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| framework | No | ||
| toVersion | Yes | ||
| fromVersion | Yes | ||
| packageChanges | Yes | ||
| renamedSymbols | Yes | ||
| breakingChanges | Yes | ||
| changedDefaults | Yes | ||
| recommendedDocs | Yes | ||
| recommendedExamples | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falseOutput schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": false,
+ "properties": {
+ "breakingChanges": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "changedDefaults": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "framework": {
+ "enum": [
+ "react",
+ "vue",
+ "angular",
+ "svelte",
+ "vanilla"
+ ],
+ "type": "string"
+ },
+ "fromVersion": {
+ "type": "string"
+ },
+ "packageChanges": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "recommendedDocs": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "authority": {
+ "type": "number"
+ },
+ "docType": {
+ "enum": [
+ "guide",
+ "api",
+ "example",
+ "live-demo",
+ "migration",
+ "faq"
+ ],
+ "type": "string"
+ },
+ "exampleUrl": {
+ "format": "uri",
+ "type": "string"
+ },
+ "framework": {
+ "enum": [
+ "react",
+ "vue",
+ "angular",
+ "svelte",
+ "vanilla"
+ ],
+ "type": "string"
+ },
+ "id": {
+ "type": "string"
+ },
+ "packageName": {
+ "type": "string"
+ },
+ "packageVersion": {
+ "type": "string"
+ },
+ "product": {
+ "enum": [
+ "core",
+ "pro",
+ "pivot",
+ "gantt",
+ "scheduler",
+ "kanban",
+ "collaboration",
+ "enterprise"
+ ],
+ "type": "string"
+ },
+ "requiresPro": {
+ "type": "boolean"
+ },
+ "score": {
+ "type": "number"
+ },
+ "snippet": {
+ "type": "string"
+ },
+ "sourcePath": {
+ "type": "string"
+ },
+ "sourceRevision": {
+ "type": "string"
+ },
+ "summary": {
+ "type": "string"
+ },
+ "surface": {
+ "enum": [
+ "core",
+ "pro",
+ "pivot",
+ "plugin",
+ "columntype",
+ "migration",
+ "changelog",
+ "internal"
+ ],
+ "type": "string"
+ },
+ "symbolKind": {
+ "enum": [
+ "class",
+ "function",
+ "interface",
+ "type",
+ "enum",
+ "variable",
+ "event",
+ "plugin",
+ "component",
+ "unknown"
+ ],
+ "type": "string"
+ },
+ "symbols": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "title": {
+ "type": "string"
+ },
+ "url": {
+ "format": "uri",
+ "type": "string"
+ },
+ "version": {
+ "type": "string"
+ },
+ "visibility": {
+ "enum": [
+ "public",
+ "internal"
+ ],
+ "type": "string"
+ },
+ "whyMatched": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "title",
+ "summary",
+ "surface",
+ "docType",
+ "requiresPro",
+ "symbols",
+ "score",
+ "snippet",
+ "url"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "recommendedExamples": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "exampleUrl": {
+ "format": "uri",
+ "type": "string"
+ },
+ "framework": {
+ "enum": [
+ "react",
+ "vue",
+ "angular",
+ "svelte",
+ "vanilla"
+ ],
+ "type": "string"
+ },
+ "id": {
+ "type": "string"
+ },
+ "packages": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "requiresPro": {
+ "type": "boolean"
+ },
+ "score": {
+ "type": "number"
+ },
+ "sourceUrl": {
+ "type": "string"
+ },
+ "summary": {
+ "type": "string"
+ },
+ "surface": {
+ "enum": [
+ "core",
+ "pro",
+ "pivot",
+ "plugin",
+ "columntype",
+ "migration",
+ "changelog",
+ "internal"
+ ],
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ },
+ "version": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "title",
+ "surface",
+ "requiresPro",
+ "summary",
+ "packages",
+ "score"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "renamedSymbols": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "from": {
+ "type": "string"
+ },
+ "to": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "from",
+ "to"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "toVersion": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "fromVersion",
+ "toVersion",
+ "breakingChanges",
+ "renamedSymbols",
+ "changedDefaults",
+ "packageChanges",
+ "recommendedDocs",
+ "recommendedExamples"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no extra behavioral context such as output format, pagination, or side effects beyond what the annotations and output schema already provide. It is consistent with annotations, so no contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. It communicates the core operation and resource efficiently, and every word contributes to the meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With annotations and an output schema present, the description does not need to explain return values or safety. However, it lacks contextual guidance for choosing this tool over sibling documentation tools and does not elaborate on the framework parameter, making it minimally adequate rather than complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It clarifies that fromVersion and toVersion are version endpoints, but it does not mention the framework parameter at all. The schema's property names and enum cover some meaning, but the description adds minimal value and leaves the optional framework parameter unexplained in prose.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb and resource: 'Get upgrade notes between RevoGrid versions.' This distinguishes it from sibling tools like inspect_revogrid_api or search_revogrid_docs by focusing specifically on version-to-version migration notes, though it does not explicitly name any sibling for contrast.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no explicit guidance on when to use this tool versus alternatives like search_revogrid_docs or resolve_feature_matrix. The intended use is only implied by the phrase 'upgrade notes between versions,' with no exclusions, prerequisites, or comparison to sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes, especially the action-oriented workflow tools like plan and validate. The main ambiguity is among the discovery/query tools—list_revogrid_capabilities, resolve_feature_matrix, search_revogrid_docs, and inspect_revogrid_api—though their descriptions provide enough guidance to avoid frequent misselection.
All tool names follow a consistent snake_case verb_noun pattern, such as find_examples, inspect_revogrid_api, and validate_revogrid_usage. The verbs clearly indicate the action, and the naming style is uniform across the entire set.
Eight tools is well-scoped for a RevoGrid implementation-assistance server. Each tool serves a meaningful step in the discovery-to-validation workflow without excessive redundancy or a feeling of missing core functionality.
The toolset covers the full knowledge-workflow lifecycle: discover capabilities, resolve feature existence, search docs, inspect exact APIs, find examples, get migration notes, plan implementation, and validate usage. This is a comprehensive surface for the stated purpose, with no obvious dead ends.