MetaSearch MCP

Normalize hotel feed

normalize_hotel_feed

Read-onlyIdempotent

Parse a hotel feed and normalize common supplier or platform aliases into a canonical hotel-record shape without changing the source payload.

Input Schema

Name	Required	Description
`format`	No	Optional input-format override. Omit or use auto to detect JSON, NDJSON, XML, CSV or TSV automatically.
`target`	No	Optional target whose parser conventions should be used while normalizing the feed. Defaults to generic hotel master data.
`content`	Yes	Feed content. Paste the JSON, XML, CSV, TSV or NDJSON payload directly. Maximum size is 2 MB.

Output Schema

Name	Required	Description	Default
`format`	Yes
`records`	Yes
`truncated`	Yes
`recordCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 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 / target / description

Added value: +"Optional target whose parser conventions should be used while normalizing the feed. Defaults to generic hotel master data."

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"
+    },
+    "recordCount": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "records": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "address": {},
+          "amenities": {},
+          "availability": {},
+          "brand": {},
+          "category": {},
+          "city": {},
+          "country": {},
+          "currency": {},
+          "description": {},
+          "id": {},
+          "image": {},
+          "latitude": {},
+          "link": {},
+          "longitude": {},
+          "name": {},
+          "phone": {},
+          "postalCode": {},
+          "price": {},
+          "province": {},
+          "sourceIndex": {
+            "maximum": 9007199254740991,
+            "minimum": 0,
+            "type": "integer"
+          },
+          "starRating": {}
+        },
+        "required": [
+          "sourceIndex"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "format",
+    "records",
+    "recordCount",
+    "truncated"
+  ],
+  "type": "object"
+}

First observedOct 8, 2026

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, and destructiveHint=false, so the safety profile is covered. The description adds real value with 'without changing the source payload', clarifying that normalization is a derived-view operation and the input is untouched. It stops short of describing how aliases are resolved or what the canonical shape contains.

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 that front-loads the action and ends with the key non-mutation guarantee. No filler and nothing redundant with the title.

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?

An output schema exists, so return values need not be explained, and the input schema is fully described. The only gap is the absence of any guidance on selecting this tool over its many validate_* and compare_* siblings, which matters given the crowded toolset.

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 format, target, and content are already fully documented in the schema. The description adds no format syntax, target semantics, or size limits beyond what the schema provides, making the baseline 3 correct.

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?

The description states a specific verb pair (parse, normalize) and resource (hotel feed), and the phrase 'canonical hotel-record shape' communicates the transformation intent. It distinguishes itself implicitly from the validate_* siblings by being a transform rather than a validator, but never names an alternative to route against.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of the sibling tools (validate_feed, detect_feed_format, suggest_feed_fixes) that an agent must choose between. The usage context is only inferable from the verb 'normalize'.

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.