Skip to main content
Glama
aws-samples

Allotrope MCP Server

by aws-samples

validate_field_map

Validate a field mapping JSON file by comparing each source value against its ASM value, returning match counts, mismatches, and a summary message.

Instructions

Validate a field mapping file produced by a custom converter script.

Reads the JSON file at ``field_map_path`` and compares each entry's
``source_value`` against its ``asm_value`` using string equality (primary)
and numeric float equality (fallback). Returns a structured JSON result
with match counts, mismatches, and a summary message.

Args:
    field_map_path: File path to the field mapping JSON file.

Returns:
    JSON string with ``matched``, ``total``, ``mismatches``, and
    ``message`` keys on success, or an ``error`` key on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
field_map_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it excels. It details the exact comparison logic (string equality primary, numeric float fallback), the file format (JSON), the return structure (match counts, mismatches, summary message), and error handling ('error' key on failure). This gives an agent a comprehensive understanding of the tool's behavior.

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?

The description is well-structured with a purpose statement, a detailed behavior section, and an Args/Returns breakdown. It is concise, front-loaded with the core purpose, and every sentence contributes valuable information without redundancy. This is a model of clear, efficient documentation.

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

Completeness5/5

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

Given the tool's moderate complexity with one parameter and an output schema, the description provides all essential context: what the tool does, how it operates, what it returns, and error behavior. The presence of an output schema means return values are additionally specified, but the description already covers them. No significant gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the parameter, and it does: 'field_map_path: File path to the field mapping JSON file.' This adds meaning beyond the bare schema definition by specifying what the path refers to and that it is a JSON file. While comprehensive for one parameter, it leaves out details like file size limits or path format, so a 4 is appropriate.

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?

The description opens with 'Validate a field mapping file produced by a custom converter script,' which clearly specifies the verb (validate) and resource (field mapping file). This distinguishes it from siblings like validate_asm_schema, which validates schemas rather than field maps. The purpose is explicit and unambiguous.

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 description provides clear context that this tool is intended for files produced by a custom converter script, indicating when it is appropriate to use. However, it does not explicitly mention alternatives or when not to use it, such as if the user needs to validate an ASM schema (validate_asm_schema). This is a minor omission, hence a 4 rather than 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aws-samples/sample-laboratory-data-transformation-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server