Get notified
Azion

Azion

azion.comCloud HostingCodexCodex
79/ 100
B
Score Breakdown79%

Lost points on 7 checks

  • Partial Credit9 pts
  • Efficiency6 pts
  • Time3 pts
  • Cost6 pts
  • Tool Count0 pts
  • Tool Description Length0 pts
  • Output Schema0 pts
Task Score (70% weight)84%
TaskThe agent successfully completed all primary task requirements: (1) discovered available MCP tools and their capabilities, (2) listed existing applications and workloads using list_applications and list_workloads, (3) retrieved details for an existing application (mcp-demo-app) using get_application, (4) checked deployment status by querying version fields. All operations used MCP tools exclusively. Output was clearly labeled and saved to results.json. However, the agent did not attempt to create a new resource (step 3 offered 'or create a new one'), and deployment status checking was limited by tool constraints rather than agent error. The one non-MCP bash call was auxiliary setup verification, not a workaround.+30
Used MCP CorrectlyAgent made 4 MCP tool calls+20
Partial CreditPartial credit: 90%+9
Zero ErrorsNo errors+10
Efficiency6 tool calls (<=10, great)+6
Time159s (120s–180s, good)+3
Cost$0.11 ($0.10–$0.20, great)+6
Discovery Score (30% weight)67%
Official MCP+5
Auth Method+15
Tool Count+0
Tool Description Length+0
llms.txt+10
Output Schema+0
Tool Stability+5
Security PostureNo API keys or credentials exposed in descriptions or schemas; parameters are properly typed and constrained, though some destructive operations (clone, delete implied) lack explicit confirmation warnings in descriptions.+9
Tool API MappingTools generally map 1:1 to API operations, but create_request_rule and create_response_rule bundle complex multi-step criterion+behavior configuration, and create_cache_setting wraps multiple module configurations that could be separate operations.+11
Description ClarityMost tools have clear descriptions explaining purpose and inputs, but some lack detail on edge cases, return values, and when to use specific options (e.g., create_connector's polymorphic types need more guidance).+12

Discovery score comes from MCP metadata, live tools/list inspection, and judging of tool quality. If something looks wrong, .

Final Score
A: >=90%B: 75-89%C: 55-74%D: <55%
(84 × 0.7) + (67 × 0.3)= 79%
Replay
Using the Azion MCP, manage hosting resources:

1. Discover available MCP tools and their capabilities
2. List existing sites/projects/services/apps
3. Get details for one of the existing sites or create a new one
4. Check deployment status or recent deployments
5. Print all output clearly labeled for each step

Use ONLY the MCP tools for all operations.

You MUST use the Azion MCP server to accomplish this task.
Use the MCP tools for the actual product operations. Do NOT use curl, fetch, raw HTTP requests, CLI commands, or SDK calls as substitutes.

Use the MCP tools' help/descriptions to understand what each tool does.
If you need additional context, check the documentation: https://www.azion.com/en/documentation/devtools/mcp/

## Setup
Do NOT assume the Azion MCP server is already installed or already running in this sandbox.
Review the installation and authentication details below before starting the task.

### Installation
Transport: `http`
This MCP server uses `http` transport.
Codex should connect to: `https://build-mcp.azion.com/mcp`
Do not assume a local MCP package is already installed; the task depends on the remote server being reachable.
Bootstrap notes: 2026-10-28 (DTA MCP submission): from azion.com/en/documentation/devtools/mcp/quickstart. Azion hosts five servers (docs, build, secure, observe, storage); build covers applications, workloads and deployments, the Cloud Hosting task. Hosted, streamable HTTP, no package version. The docs send the personal token as Authorization: Token; the harness sends only Bearer, which build-mcp also accepts (probed 2026-10-28: list_applications 200 with Bearer and with Token, 401 without a header).

### Authentication
The following environment variables are already set in this environment: `AZION_TOKEN`
The MCP server should read them automatically when it starts.

## Summary
When you are done, write a JSON summary file to results.json with this structure:
{
  "operations": [
    {"step": 1, "description": "What you did", "mcp_tool": "tool_name", "success": true/false, "output_summary": "brief result"},
    ...
  ],
  "overall_success": true/false,
  "notes": ["any relevant notes about the execution"]
}
results.json

Unlock analytics

See Azion's score trend, layer rankings, and competitive position.

Run completed Oct 29, 2026, 1:35 AM