Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Search TONE3000

tone3000_search

Search TONE3000 for NAM amp captures and cab IRs to install onto Tank-G pedal slots, filtering results by gear, make, creator, format, and sort order.

Instructions

Search TONE3000 tones. Defaults to NAM A2 captures (what the Tank-G can load). Use format='ir' for cab IRs. gears: amp, amp-cab, pedal, outboard, cab, space, experimental.

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": "tone3000_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNo
tagsNo
gearsNo
makesNoExact make/model names, e.g. 'Fender Twin Reverb'
queryNo
sizesNostandard, lite, feather, nano, custom
formatNo
creatorsNo
pageSizeNo
calibratedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses a default filter that the schema does not express (format defaults to NAM A2 captures, framed by what the Tank-G can actually load), but it says nothing about authentication, result ordering/pagination behavior, or what a result looks like.

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?

Three short sentences, front-loaded with the core action and default behavior, then the parameter hints. Nothing is repeated from the title and there is no filler.

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

Completeness2/5

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

An 11-parameter, zero-required search tool with no annotations and no output schema needs more: the return shape, how results feed the download/install siblings, and meanings for sort, sizes, calibrated and creators are all absent. The definition is a good parameter primer but not sufficient to call the tool confidently in a multi-step workflow.

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

Parameters3/5

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

Schema description coverage is only 18% across 11 parameters, so the description should compensate more. It does add genuine meaning for the two most consequential inputs by expanding 'gears' from a free-form string array into a concrete enumeration and explaining the format switch, but it leaves query, tags, sort, page, pageSize, calibrated, and creators undefined.

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 pairs the specific verb 'Search' with the resource 'TONE3000 tones' and immediately pins down scope via the default format filter. It is clearly distinguishable from retrieval siblings like tone3000_get_tone, but never names an alternative explicitly.

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?

It gives one actionable branching rule: use format='ir' for cab IRs, otherwise you get NAM A2 captures loadable by the Tank-G. That is real when-to-use guidance for a parameter choice, but there is no guidance on when this tool is the right one versus tone3000_get_tone or the download/install siblings, and no auth prerequisites are mentioned.

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