Skip to main content
Glama
Sign In
Guitar Tone Assistant

Guitar Tone Assistant

by chrissdks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get local tone profile

get_user_tone_profile
Read-only

Load a saved user profile with guitars, pickups, tunings, interface, favorite amps/IRs, and monitoring device to personalize tone recommendations and rig design.

Instructions

Read an optional local profile containing guitars, pickups, tunings, interface, favorite amps/IRs, and monitoring device.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_user_tone_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileIdNodefault

Output Schema

NameRequiredDescriptionDefault
profileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only and non-destructive behavior. The description adds useful context by noting the profile is optional and local, suggesting it may not exist and is not a remote/cloud search. No behavioral claims contradict the annotations.

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?

One tight sentence with the action and resource front-loaded; the content list is informative without padding. No redundant phrases.

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?

For a simple one-optional-parameter read tool with readOnly annotations and an output schema, the description sufficiently conveys the tool's domain. Slight gap: it doesn't explain profileId selection, but the schema's default and pattern cover invocation correctness.

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 coverage for the sole parameter is 0% and the description never mentions profileId, its default value, or when to pass a custom ID. The schema's name/default/pattern partially mitigate this, but the description itself adds no parameter-level meaning.

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?

Description uses a specific verb ('Read') and a clearly scoped resource ('optional local profile') and lists its contents (guitars, pickups, tunings, interface, amps/IRs, monitoring device), making it distinguishable from the search-oriented sibling tools.

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

Usage Guidelines4/5

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

'Read an optional local profile' provides clear context for when to call this tool: retrieving a user's saved local tone setup. It does not name alternatives or exclusions, but the 'local' qualifier implicitly distinguishes it from the search_tone3000/AmpliTube siblings and save_user_tone_profile.

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

Deploy Server

Other Tools