Skip to main content
Glama

MetaSearch MCP

by tr.com.metasearch
OverviewDiscussionsAdmin

Validate feed

validate_feed
Read-onlyIdempotent

Validate a supplied static hotel or catalog feed against one selected platform rule pack or the generic hotel master-data audit.

Input Schema

NameRequiredDescriptionDefault
formatNoOptional input-format override. Omit or use auto to detect JSON, NDJSON, XML, CSV or TSV automatically.
targetYesValidation target. Choose a published-contract validator, readiness checker or the generic hotel master data audit.
contentYesFeed content. Paste the JSON, XML, CSV, TSV or NDJSON payload directly. Maximum size is 2 MB.

Output Schema

NameRequiredDescriptionDefault
scoreYes
formatYes
issuesYes
targetYesValidation target. Choose a published-contract validator, readiness checker or the generic hotel master data audit.
recordsYes
coverageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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 / target / 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": {
+    "coverage": {
+      "additionalProperties": {
+        "additionalProperties": false,
+        "properties": {
+          "missing": {
+            "maximum": 9007199254740991,
+            "minimum": 0,
+            "type": "integer"
+          },
+          "present": {
+            "maximum": 9007199254740991,
+            "minimum": 0,
+            "type": "integer"
+          }
+        },
+        "required": [
+          "present",
+          "missing"
+        ],
+        "type": "object"
+      },
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "format": {
+      "enum": [
+        "JSON",
+        "XML",
+        "CSV",
+        "TSV",
+        "NDJSON"
+      ],
+      "type": "string"
+    },
+    "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"
+    },
+    "records": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "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"
+    }
+  },
+  "required": [
+    "target",
+    "format",
+    "records",
+    "score",
+    "issues",
+    "coverage"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

B3.4/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 openWorldHint=false, so the safety and network profile is covered. The description adds the useful 'static/supplied feed' nuance (content comes from a pasted payload, not a fetched URL), but says nothing about how results are reported, error semantics, or whether validation is purely diagnostic.

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?

A single front-loaded sentence with no filler, leading with the verb and resource before the qualifiers. The nested 'one selected platform rule pack or the generic hotel master-data audit' phrasing is dense but each clause carries meaning.

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

Completeness3/5

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

An output schema exists so return values need no explanation, and all three params are fully documented in the schema. The remaining gap is routing: the description never clarifies how this generic validator relates to the per-platform validator siblings sharing the same target values, which is the main thing an agent needs in this tool set.

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%, so the schema already explains format, target and content, including enums and the 2 MB limit. The description only adds the 'one selected' single-target constraint, which is close to restating the schema; baseline 3 is appropriate.

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 ('Validate a supplied static hotel or catalog feed') and scopes it to 'one selected platform rule pack or the generic hotel master-data audit', which signals it is the general-purpose dispatcher. It does not, however, acknowledge the per-platform siblings (validate_wego_hotel_feed, validate_google_hotel_center_list, etc.) that cover the same targets, so an agent cannot fully disambiguate from the text alone.

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?

Usage is implied by the target selection ('one selected platform rule pack or the generic hotel master-data audit' plus the single-target wording), so an agent can infer it must pick one target. But there is no explicit when-to-use vs when-not, and nothing routes the agent to the equivalent platform-specific validator siblings that share the same target enum.

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

All MetaSearch MCP toolsInspect
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.

Resources