MetaSearch MCP

Detect feed format

detect_feed_format

Read-onlyIdempotent

Detect whether a supplied hotel or catalog feed payload is JSON, NDJSON, XML, CSV or TSV before parsing or validation.

Input Schema

Name	Required	Description	Default
`content`	Yes	Feed content. Paste the JSON, XML, CSV, TSV or NDJSON payload directly. Maximum size is 2 MB.
`formatHint`	No	Optional expected format hint. Omit or use auto when the format should be detected from the payload.

Output Schema

Name	Required	Description	Default
`format`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 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 / formatHint / description

Added value: +"Optional expected format hint. Omit or use auto when the format should be detected from the payload."

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"
+    }
+  },
+  "required": [
+    "format"
+  ],
+  "type": "object"
+}

First observedOct 8, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered; the description's contribution beyond that is limited to reinforcing that this is a pre-processing detection step. It says nothing about conflict handling when formatHint disagrees with the payload, or about ambiguity/mixed-format behavior. Added value over structured fields 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 front-loaded sentence with zero filler; the verb, the resource, the format enumeration, and the pipeline position are all packed in without redundancy.

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 an output schema present, the description need not describe return values, and the two-parameter schema is fully documented. What remains missing is guidance on formatHint-conflict resolution and low-confidence detection, which is minor for a stateless detection utility. Nearly complete for the tool's complexity.

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% for both parameters, including the 2 MB maxLength and the enum semantics of formatHint, so the schema does the heavy lifting. The description mentions the payload and the format set but adds no syntax, precedence, or edge-case guidance beyond what the schema already states. Baseline 3 applies.

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?

States a specific verb (Detect) and resource (feed format), enumerates the candidate formats (JSON, NDJSON, XML, CSV, TSV), and positions the tool relative to the validate_* siblings by saying it runs 'before parsing or validation'. An agent can distinguish it from validate_feed and normalize_hotel_feed without opening any schema.

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

Usage Guidelines4/5

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

The phrase 'before parsing or validation' clearly signals the pipeline stage at which this tool belongs, implicitly routing the agent away from the validate_* siblings. It does not name an explicit alternative or state exclusion conditions, so it falls short of a 5.

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.