Guitar Tone Assistant

Compare TONE3000 tones

compare_tones

Read-only

Compare two to four TONE3000 tone packs by gain clues, EQ clues, cab requirements, flexibility, and likely use. Identify the best match for your rig with direct links to each pack.

Instructions

Compare two to four TONE3000 tone packs by gain clues, EQ clues, cab requirements, flexibility, and likely use. Uses metadata conservatively and returns direct links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tones": "<tones>"
    },
    "name": "compare_tones"
  }
}

Input Schema

Name	Required	Description	Default
`tones`	Yes
`architecture`	No

Output Schema

Name	Required	Description	Default
`rows`	Yes
`guidance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already establish the tool as read-only and non-destructive. The description adds useful behavioral context by noting it 'uses metadata conservatively and returns direct links,' which hints at output style and reliance on metadata. However, 'conservatively' is vague and the full behavioral implications are not developed.

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 two sentences with no redundancy. The primary purpose is front-loaded, and the second sentence efficiently adds behavioral detail about metadata usage and output format.

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

Completeness3/5

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

For a moderate-complexity tool with an output schema, the description covers the core comparison intent and output style. However, it omits guidance on when to use the tool versus siblings and leaves the architecture parameter unexplained, so the agent may not fully understand all inputs or selection criteria.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for parameter meaning. It does explain that tones are limited to two to four packs, but it does not clarify what the architecture parameter ('1', '2', 'custom') means, nor what types of identifiers are accepted in the tones array. This leaves a significant semantic gap.

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 states a specific verb ('Compare'), a precise resource ('two to four TONE3000 tone packs'), and the dimensions of comparison ('gain clues, EQ clues, cab requirements, flexibility, likely use'). This clearly distinguishes it from sibling tools like search, get, recommend, and troubleshoot.

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

Usage Guidelines3/5

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

The description implies the tool is for comparing a limited set of existing tone packs, which is useful context. However, it does not explicitly state when to prefer this over alternatives such as search_tone3000 or recommend_tone_chain, nor does it mention any exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server