MetaSearch MCP

Compare feed readiness

compare_feed_readiness

Read-onlyIdempotent

Run the same static feed through multiple platform rule packs and compare readiness scores, errors, warnings and validation issues.

Input Schema

Name	Required	Description
`format`	No	Optional input-format override. Omit or use auto to detect JSON, NDJSON, XML, CSV or TSV automatically.
`content`	Yes	Feed content. Paste the JSON, XML, CSV, TSV or NDJSON payload directly. Maximum size is 2 MB.
`targets`	No	Optional list of validation targets. Omit to use every supported target.

Output Schema

Name	Required	Description	Default
`format`	Yes
`records`	Yes
`targets`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 9, 2026

changedInput schema / properties / content / description

Previous value: -"Feed content. Paste the JSON, XML, CSV, TSV or NDJSON payload directly."New value: +"Feed content. Paste the JSON, XML, CSV, TSV or NDJSON payload directly. Maximum size is 2 MB."

addedInput schema / properties / format / description

Added value: +"Optional input-format override. Omit or use auto to detect JSON, NDJSON, XML, CSV or TSV automatically."

addedInput schema / properties / targets / description

Added value: +"Optional list of validation targets. Omit to use every supported target."

addedInput schema / properties / targets / items / description

Added value: +"Validation target. Choose a published-contract validator, readiness checker or the generic hotel master data audit."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "format": {
+      "enum": [
+        "JSON",
+        "XML",
+        "CSV",
+        "TSV",
+        "NDJSON"
+      ],
+      "type": "string"
+    },
+    "records": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "targets": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "errors": {
+            "maximum": 9007199254740991,
+            "minimum": 0,
+            "type": "integer"
+          },
+          "issues": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "code": {
+                  "type": "string"
+                },
+                "level": {
+                  "enum": [
+                    "error",
+                    "warning",
+                    "info"
+                  ],
+                  "type": "string"
+                },
+                "message": {
+                  "type": "string"
+                },
+                "rows": {
+                  "items": {
+                    "maximum": 9007199254740991,
+                    "minimum": 0,
+                    "type": "integer"
+                  },
+                  "type": "array"
+                }
+              },
+              "required": [
+                "level",
+                "code",
+                "message"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "score": {
+            "maximum": 100,
+            "minimum": 0,
+            "type": "number"
+          },
+          "target": {
+            "description": "Validation target. Choose a published-contract validator, readiness checker or the generic hotel master data audit.",
+            "enum": [
+              "wego",
+              "google_hotel_center",
+              "trivago",
+              "meta_catalog",
+              "criteo",
+              "hotel_master_data"
+            ],
+            "type": "string"
+          },
+          "warnings": {
+            "maximum": 9007199254740991,
+            "minimum": 0,
+            "type": "integer"
+          }
+        },
+        "required": [
+          "target",
+          "score",
+          "errors",
+          "warnings",
+          "issues"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "records",
+    "format",
+    "targets"
+  ],
+  "type": "object"
+}

First observedOct 8, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the output is a comparison of readiness scores, errors, warnings and issues across packs, but the return shape is already covered by the output schema, so net additional behavioral disclosure is modest.

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?

A single tight sentence with the verb front-loaded and no filler. Every clause (same feed, multiple packs, compared scores/errors/warnings/issues) carries information.

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?

With a full-coverage schema, an output schema, and rich read-only annotations, the description supplies everything an agent needs to select and call the tool. Minor omission: no hint about relative cost or latency when fanning out across up to six targets, which is the main behavioral risk of a comparison tool.

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 description coverage is 100% and the schema already documents the format override, 2 MB content limit, and the optional targets list with its enum and 'omit for all targets' default. The description contributes only the general framing of 'multiple platform rule packs', which maps loosely to targets but adds no syntax or constraint detail 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?

Names a precise verb-resource pair ('run the same static feed through multiple platform rule packs and compare readiness scores') and clearly distinguishes itself from the single-target validate_* siblings by virtue of being a multi-pack comparison. An agent can tell it apart from validate_feed or validate_wego_hotel_feed without opening a schema.

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?

Implied usage is clear: use this when you want one feed checked against several platforms at once rather than a single validator. However, it never names an alternative tool (e.g. validate_feed for single-target checks or compare_platform_requirements for requirement-level questions) or states when comparison is not appropriate, so the routing guidance is left to inference.

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

All MetaSearch MCP tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.