Skip to main content
Glama
verIdyia

AutoEQ MCP Server

by verIdyia

eq_targets

Read-onlyIdempotent

List available EQ target curves like Harman and Diffuse Field to help users select appropriate equalization presets for audio optimization.

Instructions

List all available EQ target curves (Harman, Diffuse Field, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The eq_targets tool handler, which queries the database for target curves and formats them by category.
    async def eq_targets() -> str:
        """List all available EQ target curves (Harman, Diffuse Field, etc.)."""
        conn = get_db()
        rows = conn.execute("SELECT name FROM targets ORDER BY name").fetchall()
        conn.close()
    
        if not rows:
            return "No target data. Run eq_sync first."
    
        lines = ["## Available target curves"]
        categories = {"Harman": [], "Diffuse Field": [], "AutoEq": [], "Other": []}
        for r in rows:
            name = r["name"]
            if "Harman" in name or "harman" in name:
                categories["Harman"].append(name)
            elif "Diffuse" in name:
                categories["Diffuse Field"].append(name)
            elif "AutoEq" in name:
                categories["AutoEq"].append(name)
            else:
                categories["Other"].append(name)
    
        for cat, names in categories.items():
            if names:
                lines.append(f"\n### {cat}")
                for n in names:
                    lines.append(f"- {n}")
    
        return "\n".join(lines)
  • autoeq_mcp.py:886-895 (registration)
    Registration of the eq_targets tool using the mcp_server.tool decorator.
    @mcp_server.tool(
        name="eq_targets",
        annotations={
            "title": "List target curves",
            "readOnlyHint": True,
            "destructiveHint": False,
            "idempotentHint": True,
            "openWorldHint": False,
        },
    )
Behavior3/5

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

The description adds minimal behavioral context beyond annotations. Annotations already indicate this is a read-only, non-destructive, idempotent operation with a closed world. The description only specifies what is listed (EQ target curves with examples), which is useful but not rich in behavioral details like rate limits or authentication needs.

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?

The description is a single, efficient sentence that directly states the tool's function with no wasted words. It's front-loaded with the core action and includes helpful examples, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, read-only operation) and the presence of annotations and an output schema, the description is reasonably complete. It specifies what is listed, though it could benefit from more context on how this differs from sibling tools to fully guide the agent.

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?

With 0 parameters and 100% schema description coverage, the schema fully documents the input (none required). The description doesn't need to add parameter semantics, and it appropriately doesn't mention any, earning a baseline score of 4 for this context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with the verb 'List' and resource 'EQ target curves', and provides examples of what those curves include (Harman, Diffuse Field, etc.). However, it doesn't explicitly differentiate this tool from its siblings like eq_search or eq_compare, which might also involve EQ targets in some way.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus its siblings. It doesn't mention alternatives, prerequisites, or any context for usage, leaving the agent to infer based on the tool name alone.

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/verIdyia/autoeq-mcp'

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