Skip to main content
Glama
cyberbuff

Atomic Red Team MCP

by cyberbuff
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

refresh_atomics

Idempotent

Refresh atomic tests from the GitHub repository, replacing local copies and reloading them into memory for immediate querying and execution.

Instructions

Download and reload atomic tests from the GitHub repository.

This tool forces a fresh download of all atomic tests from the configured GitHub repository, replacing any existing local copies. It then reloads all tests into memory, making them immediately available for querying and execution.

Use this tool when:

  • You want to get the latest atomic tests from the repository

  • Custom atomic tests were added to the data directory

  • The atomic test database needs to be refreshed

  • You suspect the loaded tests are out of sync with the repository

Args: ctx: MCP context (provided automatically by the framework) progress: Background task progress reporter (injected automatically)

Returns: RefreshAtomicsOutput: Structured output containing: - success (bool): Whether the refresh operation completed successfully - message (str): Human-readable message about the refresh operation - atomics_count (int): Number of atomic tests loaded after refresh - repository_url (str): GitHub repository URL that was used for refresh

Process: 1. Deletes existing atomic tests directory (if present) 2. Clones the GitHub repository (configured via ART_GITHUB_* settings) 3. Extracts the atomics directory from the repository 4. Parses all YAML files and validates them 5. Loads atomic tests into server memory 6. Makes tests immediately available to other tools

Configuration: The repository location is controlled by environment variables: - ART_GITHUB_URL: Base GitHub URL (default: https://github.com) - ART_GITHUB_USER: User/organization (default: redcanaryco) - ART_GITHUB_REPO: Repository name (default: atomic-red-team) - ART_DATA_DIR: Local storage path (default: ./atomics)

Examples: # Refresh from default repository refresh_atomics(ctx)

# After setting custom repo in .env:
# ART_GITHUB_USER=your-org
# ART_GITHUB_REPO=custom-atomics
refresh_atomics(ctx)

Notes: - This operation may take 30-60 seconds depending on network speed - Runs as a background task — the client receives a task ID immediately and can poll for completion - Requires internet connectivity to GitHub - Overwrites any local modifications to atomic tests - The repository is cloned with depth=1 for efficiency (only latest commit) - Failed YAML files are logged but don't stop the overall refresh

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesHuman-readable message about the refresh operation
successYesWhether the refresh operation completed successfully
atomics_countYesNumber of atomic tests loaded after refresh
repository_urlYesGitHub repository URL that was used for refresh

Tool Definition Quality

A4.2/5.0
Behavior1/5

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

The description explicitly states the tool will 'Deletes existing atomic tests directory', 'Overwrites any local modifications', and 'replaces existing local copies', all of which indicate destructive actions. However, the annotation sets destructiveHint=false, which directly contradicts this behavioral disclosure. Per the scoring rules, this contradiction forces a score of 1 on this dimension.

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?

Despite being long, the description is excellently structured with labeled sections (Overview, Use when, Args, Returns, Process, Configuration, Examples, Notes). It front-loads the core purpose, and every section conveys actionable details without redundancy or filler.

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 description covers the six-step process, environment configuration, example invocations, runtime expectations, background execution, error tolerance for YAML failures, and the exact output fields. This level of detail, combined with the output schema, fully contextualizes the tool for an agent with no prior knowledge.

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

Parameters5/5

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

The input schema has zero properties, and the description explains that ctx and progress are automatically injected by the framework. This clarifies the empty schema, confirming no user-supplied parameters are needed and adds meaningful context about the automatic injection mechanism.

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 phrase 'Download and reload atomic tests from the GitHub repository', clearly naming both the action and the resource. It distinguishes itself from sibling tools like query_atomics, validate_atomic, and generate_atomic by focusing solely on refreshing the local test data.

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

Usage Guidelines5/5

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

The 'Use this tool when' section provides four concrete, scenario-based conditions for when to invoke this tool. It also implicitly warns against expecting a fast operation and notes prerequisites like internet connectivity and the overwrite of local modifications, effectively guiding the agent on when this tool is appropriate.

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