Skip to main content
Glama
cyberbuff

Atomic Red Team MCP

by cyberbuff

get_validation_schema

Read-onlyIdempotent

Retrieve the JSON schema for atomic tests, defining required fields, data types, and validation rules. Use it to create or modify tests that meet quality standards.

Instructions

Get the JSON schema that defines the structure and requirements for atomic tests.

This schema provides the complete specification for creating valid atomic tests. It defines all fields (required and optional), data types, validation rules, and constraints. Use this as a reference when creating or modifying atomic tests to ensure they meet quality standards.

The schema follows the Atomic Red Team YAML format and is automatically generated from the Pydantic models, ensuring it's always in sync with validation rules.

Returns: dict: JSON Schema (Draft 7) containing: - definitions: Nested object definitions (Executor, Dependency, etc.) - properties: Field definitions with types and constraints - required: List of mandatory fields - additionalProperties: Whether extra fields are allowed - field descriptions: Human-readable explanations for each field

Schema Structure: The schema defines these main sections: - name: Test name (required, min 1 character) - description: Test explanation (required, min 1 character) - supported_platforms: Platform list (required, min 1 platform) - executor: Execution method (required, CommandExecutor or ManualExecutor) - input_arguments: Parameterized inputs (optional, dict) - dependencies: Prerequisites (optional, list) - dependency_executor_name: Executor for dependencies (optional) - auto_generated_guid: Unique ID (optional, auto-generated)

Examples: # Get the schema schema = get_validation_schema()

# Check required fields
required_fields = schema['required']
print(f"Required fields: {required_fields}")

# View field definitions
properties = schema['properties']
print(f"Available fields: {list(properties.keys())}")

# Check platform options
platform_enum = schema['definitions']['Platform']['enum']
print(f"Valid platforms: {platform_enum}")

Common Use Cases: 1. Creating new tests: Reference required fields and formats 2. Understanding validation: See what rules will be enforced 3. Tool development: Use schema for code generation 4. Documentation: Generate field descriptions automatically

Notes: - Schema is generated from Pydantic models at runtime - Always reflects current validation rules - Includes custom validators and constraints - Follows JSON Schema Draft 7 specification - Can be used with JSON Schema validators in any language - Do not add comments to the created atomic test

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds extra value by disclosing that the schema is generated at runtime from Pydantic models, is always in sync, and includes a note against adding comments. This goes beyond the basic safety profile.

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 long but well-structured into sections (schema structure, examples, use cases, notes). The first sentence delivers the core purpose, and each section adds practical information. Slightly verbose for a no-parameter tool, but the content justifies the length.

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?

The tool is simple, but the description goes beyond the minimum by detailing the return value structure, providing code examples, and explaining how the schema is generated. With a full output schema and a comprehensive description, nothing important is left unstated.

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?

The tool has zero parameters, so schema coverage is trivially 100%. The description does not need to explain parameters and instead focuses on return value structure, which is appropriate for a no-argument tool.

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: 'Get the JSON schema that defines the structure and requirements for atomic tests.' This clearly distinguishes the tool from siblings like validate_atomic or generate_atomic by its unique purpose.

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 explicitly states 'Use this as a reference when creating or modifying atomic tests to ensure they meet quality standards' and lists common use cases. While it doesn't explicitly name alternatives, the context makes it clear this is the schema-reference tool, not a validation or generation tool.

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/cyberbuff/atomic-red-team-mcp'

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