Aria Tool Patterns

ARIA Tool Patterns Reference

This is background knowledge about how ARIA MCP tools are structured. Apply these patterns when creating, modifying, or reviewing tools.

Required Structure

Every tool file in ARIA/agent/tools/ must follow this structure:

"""Module docstring — one-line purpose."""

from __future__ import annotations

from claude_agent_sdk import tool

from agent.observability import get_tracer

tracer = get_tracer()


@tool(
    name="tool_name",
    description="Detailed description for Claude to know when/how to use this tool.",
    input_schema={"param": type},
)
async def tool_function(args: dict) -> dict:
    """Function docstring."""
    with tracer.start_as_current_span("module.operation") as span:
        param = args.get("param", default)
        span.set_attribute("aria.domain.param", param)

        # Logic here
        result = {}

        span.set_attribute("aria.domain.output", value)
        return {"content": [{"type": "text", "text": str(result)}]}

Naming Conventions