Skip to main content
Glama
aws-samples

Allotrope MCP Server

by aws-samples

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
validate_field_mapA

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.
validate_asm_schemaA

Validate an ASM JSON document against an Allotrope JSON Schema.

Args:
    asm_document_path: File path to the ASM JSON document.
    asm_schema_path: File path to the ASM JSON Schema.

Returns:
    JSON string with validation result.
fetch_asm_documentA

Fetch a raw ASM JSON document from purl.allotrope.org.

Downloads the document identified by ``asm_document_uri`` from the Allotrope
PURL repository and saves it to the local filesystem at a path that mirrors
the URI structure.  If the file already exists it is returned immediately
without re-downloading. ``$ref`` references are
NOT resolved — the document is saved exactly as received.

Args:
    asm_document_uri: Fully-qualified URI starting with
        ``http://purl.allotrope.org``.
    output_dir: Base directory for saving the document.  Defaults to the
        current working directory when empty.

Returns:
    JSON string with a ``path`` key containing the absolute path to the
    saved file, or an ``error`` key with a description on failure.
list_asmsA

List all available Allotrope Simple Models (ASMs).

Retrieves ASM identifiers and descriptions from the local
model_reference.json file bundled with the package.

Returns:
    JSON string with ASM IDs mapped to descriptions, or an
    error key with a description on failure.
describe_asmA

Return the metadata for a specific ASM model by name.

Args:
    model_name: The key identifying the ASM model (e.g. 'automated-reactors').

Returns:
    JSON string containing the model metadata on success, or an error object
    with the unrecognized name and a list of valid model names on failure.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct resource and action: validate_field_map checks field mappings, validate_asm_schema validates an ASM document against a schema, fetch_asm_document downloads a raw ASM document, list_asms enumerates models, and describe_asm provides metadata for a specific model. There is no meaningful overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case: validate_field_map, validate_asm_schema, fetch_asm_document, list_asms, describe_asm. The minor difference in singular/plural (asm/asms) is natural and does not create confusion.

Tool Count5/5

Five tools is well within the ideal 3-15 range and each tool serves a clear, non-redundant function. The count feels appropriately scoped for a server focused on ASM validation and metadata retrieval.

Completeness4/5

The server covers the core workflows of discovering ASM models, fetching documents, validating schemas, and validating field maps. A minor gap is the lack of a tool to fetch schemas directly, but this can be worked around since validate_asm_schema accepts a local schema path.

Maintenance

ActivityInactive
ResponsivenessNo issues