Skip to main content
Glama

required_fields

List the 10 required AI-BOM field categories and their fields to standardize AI system documentation.

Instructions

List the 10 required AI-BOM field categories and their fields.

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results.

Args: api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'required_fields' tool handler function. It checks access, then returns the AI_BOM_REQUIRED_FIELDS dictionary listing all 10 required field categories and their fields, along with source standards and supported formats.
    @mcp.tool()
    def required_fields(api_key: str = "") -> str:
        """List the 10 required AI-BOM field categories and their fields.
    
        Behavior:
            This tool is read-only and stateless — it produces analysis output
            without modifying any external systems, databases, or files.
            Safe to call repeatedly with identical inputs (idempotent).
            Free tier: 10/day rate limit. Pro tier: unlimited.
            No authentication required for basic usage.
    
        When to use:
            Use this tool when you need structured analysis or classification
            of inputs against established frameworks or standards.
    
        When NOT to use:
            Not suitable for real-time production decision-making without
            human review of results.
    
        Args:
            api_key (str): The api key to analyze or process.
    
        Behavioral Transparency:
            - Side Effects: This tool is read-only and produces no side effects. It does not modify
              any external state, databases, or files. All output is computed in-memory and returned
              directly to the caller.
            - Authentication: No authentication required for basic usage. Pro/Enterprise tiers
              require a valid MEOK API key passed via the MEOK_API_KEY environment variable.
            - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are
              included in responses (X-RateLimit-Remaining, X-RateLimit-Reset).
            - Error Handling: Returns structured error objects with 'error' key on failure.
              Never raises unhandled exceptions. Invalid inputs return descriptive validation errors.
            - Idempotency: Fully idempotent — calling with the same inputs always produces the
              same output. Safe to retry on timeout or transient failure.
            - Data Privacy: No input data is stored, logged, or transmitted to external services.
              All processing happens locally within the MCP server process.
        """
        allowed, msg, tier = check_access(api_key)
        if not allowed:
            return json.dumps({"error": msg})
        return json.dumps({
            "source": "NIST SP 800-218 SSDF + CISA AI Cyber Report 2024 + EU AI Act Annex IV + CycloneDX 1.6 ML-BOM",
            "required_categories": AI_BOM_REQUIRED_FIELDS,
            "formats_supported": ["CycloneDX 1.6 ML-BOM (recommended)", "SPDX 3.0.1 AI profile"],
        }, indent=2)
  • The AI_BOM_REQUIRED_FIELDS dictionary that defines the schema/data model for the 'required_fields' tool. It contains 10 categories (model_identity, model_architecture, training_data, fine_tuning, evaluation, dependencies, security_controls, governance, usage_restrictions, distribution) each with their required sub-fields.
    AI_BOM_REQUIRED_FIELDS = {
        "model_identity": ["name", "version", "organisation", "licence", "release_date", "model_id_hash"],
        "model_architecture": ["architecture_type", "parameter_count", "context_window", "framework", "training_compute_flops"],
        "training_data": ["dataset_sources", "dataset_sizes", "data_provenance", "filtering_applied", "synthetic_data_percent", "copyright_status"],
        "fine_tuning": ["base_model", "fine_tune_method", "fine_tune_dataset", "fine_tune_steps", "rlhf_applied"],
        "evaluation": ["benchmarks_run", "benchmark_scores", "bias_testing_results", "red_team_findings", "eval_dataset_hash"],
        "dependencies": ["inference_engines", "tokenisers", "safety_filters", "retrieval_systems", "tools_registered"],
        "security_controls": ["prompt_injection_defence", "output_filtering", "pii_scrubbing", "adversarial_robustness_rating"],
        "governance": ["risk_classification", "regulations_applicable", "human_oversight_mechanism", "incident_reporting_contact"],
        "usage_restrictions": ["acceptable_use_policy", "prohibited_use_cases", "export_control_status", "region_restrictions"],
        "distribution": ["distribution_channels", "access_controls", "update_cadence", "decommissioning_policy"],
    }
  • server.py:428-429 (registration)
    The tool is registered with the MCP framework using the @mcp.tool() decorator on line 428, which makes the 'required_fields' function available as an MCP tool.
    @mcp.tool()
    def required_fields(api_key: str = "") -> str:
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: read-only/stateless, rate limits (free 10/day, Pro unlimited), no authentication required, idempotency, error handling returning structured errors, and data privacy (no storage/transmission). This is exceptionally thorough.

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?

The description is well-structured with clear sections (behavior, when to use, args, behavioral transparency). However, there is redundancy: the 'Behavior' section repeats the same read-only/stateless/rate limit info later in 'Behavioral Transparency.' Still, it remains organized and mostly front-loaded with the purpose.

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?

For a simple listing tool, the description covers all necessary context: purpose, behavior, rate limits, authentication, error handling, idempotency, and data privacy. An output schema exists (not shown), but the description provides enough cues for safe invocation without needing it.

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

Parameters2/5

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

The input schema has 0% description coverage (no parameter descriptions), so the description must compensate. It only states 'api_key (str): The api key to analyze or process,' which adds minimal meaning—it does not clarify its optional role given 'no authentication required for basic usage.' The compensation is inadequate.

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 a specific verb-resource pair ('List the 10 required AI-BOM field categories and their fields'), clearly stating what the tool does. This distinct purpose differentiates it from siblings like 'audit_ai_bom_completeness' and 'generate_ai_bom' without needing explicit comparison.

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 includes dedicated 'When to use' and 'When NOT to use' sections, providing clear context for appropriate usage. It advises against real-time production use without human review, but does not explicitly name alternative sibling tools, so it lacks direct differentiation.

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/CSOAI-ORG/ai-bom-mcp'

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