resolve_feature_matrixResolve whether a RevoGrid feature exists, whether it is Pro, and where to learn it.
| Name | Required | Description | Default |
|---|---|---|---|
| version | No | ||
| framework | No | ||
| featureName | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| notes | Yes | ||
| bestDocs | Yes | ||
| stability | No | ||
| supported | Yes | ||
| featureName | Yes | ||
| requiresPro | Yes | ||
| bestExamples | Yes | ||
| fallbackApproach | No | ||
| supportedFrameworks | 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": {
+ "bestDocs": {
+ "default": [],
+ "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"
+ },
+ "bestExamples": {
+ "default": [],
+ "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"
+ },
+ "fallbackApproach": {
+ "type": "string"
+ },
+ "featureName": {
+ "type": "string"
+ },
+ "notes": {
+ "default": [],
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "requiresPro": {
+ "type": "boolean"
+ },
+ "stability": {
+ "enum": [
+ "stable",
+ "experimental",
+ "deprecated"
+ ],
+ "type": "string"
+ },
+ "supported": {
+ "type": "boolean"
+ },
+ "supportedFrameworks": {
+ "items": {
+ "enum": [
+ "react",
+ "vue",
+ "angular",
+ "svelte",
+ "vanilla"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "featureName",
+ "supported",
+ "requiresPro",
+ "supportedFrameworks",
+ "notes",
+ "bestDocs",
+ "bestExamples"
+ ],
+ "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 context by specifying the resolution outputs, but it does not disclose details such as the data source or whether the resolution is static. No contradiction with annotations.
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 states the action and the three key outcomes clearly, making every word carry 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?
The output schema and annotations cover the return shape and safety profile, which reduces the burden on the description. However, the description does not explain how the optional version and framework parameters influence the lookup, nor does it position the tool against its seven siblings. Adequate but not fully 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 implies that featureName is the core parameter, but it gives no explanation of how version or framework affect the feature matrix resolution. The agent is left to infer their meaning from the schema's enum and optionality.
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 uses a specific verb ('Resolve') and names the exact outputs: whether a RevoGrid feature exists, whether it is Pro, and where to learn it. This is clear enough to differentiate it from broader siblings like list_revogrid_capabilities, though it does not explicitly name any alternative.
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?
There is no explicit guidance on when to use this tool versus alternatives like search_revogrid_docs or validate_revogrid_usage. The intended usage is implied by the action verb, but no prerequisites, exclusions, or routing conditions are provided.
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.