Skip to main content
Glama

Learn Moose Tracker

describe
Read-onlyIdempotent

Use this when the user asks for a sound effect, click, notification, jingle, audio, music, song or soundtrack, or mentions Moose Tracker: returns usage notes. No arguments gives a short index (workflow, limits, formats, next steps); topic opens one section: syntax, limits, styles, recipes, presets, mtl, instrument, effects, modulation, drums, loops, formats, sfx, examples, errors, genres, generators, samples, search, not_supported, workflow, volume, mix, sounds, character; q searches presets and the sample library; with topic="syntax", q opens one syntax section (q="arp") or a field. Song text up to 256 KB; one audio file holds about 8 min as WAV, longer as Ogg or Opus (exact seconds per format in the index). Tool list 1.6.1. Schema a964948f.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch word, example id, role for topic=instrument; for samples also category=X genre=Y
genreNotopic=samples: only packs for this genre
limitNo
topicNo
cursorNo
detailNo
categoryNotopic=samples: only this category (drums, keys, pads, ...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 826121bd"New value: +"Schema a964948f"
  2. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2d544474"New value: +"Schema 826121bd"
  3. Changed2 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema 0781812e"New value: +"Schema 2d544474"
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "syntax",
      -  "limits",
      -  "styles",
      -  "recipes",
      -  "presets",
      -  "mtl",
      -  "instrument",
      -  "effects",
      -  "modulation",
      -  "drums",
      -  "loops",
      -  "formats",
      -  "sfx",
      -  "examples",
      -  "errors",
      -  "genres",
      -  "generators",
      -  "samples",
      -  "search",
      -  "not_supported",
      -  "workflow",
      -  "volume",
      -  "mix",
      -  "sounds"
      -]New value: +[
      +  "syntax",
      +  "limits",
      +  "styles",
      +  "recipes",
      +  "presets",
      +  "mtl",
      +  "instrument",
      +  "effects",
      +  "modulation",
      +  "drums",
      +  "loops",
      +  "formats",
      +  "sfx",
      +  "examples",
      +  "errors",
      +  "genres",
      +  "generators",
      +  "samples",
      +  "search",
      +  "not_supported",
      +  "workflow",
      +  "volume",
      +  "mix",
      +  "sounds",
      +  "character"
      +]
  4. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 0d11f08d"New value: +"Schema 0781812e"
  5. Changed2 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema 2d7abb8b"New value: +"Schema 0d11f08d"
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "limits",
      -  "styles",
      -  "recipes",
      -  "presets",
      -  "mtl",
      -  "instrument",
      -  "effects",
      -  "modulation",
      -  "drums",
      -  "loops",
      -  "formats",
      -  "sfx",
      -  "examples",
      -  "errors",
      -  "genres",
      -  "generators",
      -  "samples",
      -  "search",
      -  "not_supported",
      -  "workflow",
      -  "volume",
      -  "mix",
      -  "sounds"
      -]New value: +[
      +  "syntax",
      +  "limits",
      +  "styles",
      +  "recipes",
      +  "presets",
      +  "mtl",
      +  "instrument",
      +  "effects",
      +  "modulation",
      +  "drums",
      +  "loops",
      +  "formats",
      +  "sfx",
      +  "examples",
      +  "errors",
      +  "genres",
      +  "generators",
      +  "samples",
      +  "search",
      +  "not_supported",
      +  "workflow",
      +  "volume",
      +  "mix",
      +  "sounds"
      +]
  6. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema ff675289"New value: +"Schema 2d7abb8b"
  7. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2a55f659"New value: +"Schema ff675289"
  8. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 71227a86"New value: +"Schema 2a55f659"
  9. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 64bfe66c"New value: +"Schema 71227a86"
  10. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema eb59845f"New value: +"Schema 64bfe66c"
  11. Changed2 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema 3b8fe45c"New value: +"Schema eb59845f"
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "limits",
      -  "styles",
      -  "recipes",
      -  "presets",
      -  "mtl",
      -  "instrument",
      -  "effects",
      -  "modulation",
      -  "drums",
      -  "loops",
      -  "formats",
      -  "sfx",
      -  "examples",
      -  "errors",
      -  "genres",
      -  "generators",
      -  "samples",
      -  "search",
      -  "not_supported",
      -  "workflow",
      -  "volume",
      -  "mix"
      -]New value: +[
      +  "limits",
      +  "styles",
      +  "recipes",
      +  "presets",
      +  "mtl",
      +  "instrument",
      +  "effects",
      +  "modulation",
      +  "drums",
      +  "loops",
      +  "formats",
      +  "sfx",
      +  "examples",
      +  "errors",
      +  "genres",
      +  "generators",
      +  "samples",
      +  "search",
      +  "not_supported",
      +  "workflow",
      +  "volume",
      +  "mix",
      +  "sounds"
      +]
  12. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 9b20e675"New value: +"Schema 3b8fe45c"
  13. Changed2 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema 415a8741"New value: +"Schema 9b20e675"
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "limits",
      -  "styles",
      -  "recipes",
      -  "presets",
      -  "mtl",
      -  "instrument",
      -  "effects",
      -  "modulation",
      -  "drums",
      -  "loops",
      -  "formats",
      -  "sfx",
      -  "examples",
      -  "errors",
      -  "genres",
      -  "generators",
      -  "samples",
      -  "search",
      -  "not_supported"
      -]New value: +[
      +  "limits",
      +  "styles",
      +  "recipes",
      +  "presets",
      +  "mtl",
      +  "instrument",
      +  "effects",
      +  "modulation",
      +  "drums",
      +  "loops",
      +  "formats",
      +  "sfx",
      +  "examples",
      +  "errors",
      +  "genres",
      +  "generators",
      +  "samples",
      +  "search",
      +  "not_supported",
      +  "workflow",
      +  "volume",
      +  "mix"
      +]
  14. Changed4 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema d568427c"New value: +"Schema 415a8741"
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "topic=samples: only this category (drums, keys, pads, ...)",
      +  "type": "string"
      +}
    • addedInput schema / properties / genre
      Added value: +{
      +  "description": "topic=samples: only packs for this genre",
      +  "type": "string"
      +}
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "limits",
      -  "styles",
      -  "recipes",
      -  "presets",
      -  "mtl",
      -  "instrument",
      -  "effects",
      -  "modulation",
      -  "drums",
      -  "loops",
      -  "formats",
      -  "sfx",
      -  "examples",
      -  "errors",
      -  "genres",
      -  "generators",
      -  "samples",
      -  "not_supported"
      -]New value: +[
      +  "limits",
      +  "styles",
      +  "recipes",
      +  "presets",
      +  "mtl",
      +  "instrument",
      +  "effects",
      +  "modulation",
      +  "drums",
      +  "loops",
      +  "formats",
      +  "sfx",
      +  "examples",
      +  "errors",
      +  "genres",
      +  "generators",
      +  "samples",
      +  "search",
      +  "not_supported"
      +]
  15. Changed3 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema 90ddc268"New value: +"Schema d568427c"
    • changedInput schema / properties / q / description
      Previous value: -"Search word, example id, or role for topic=instrument"New value: +"Search word, example id, role for topic=instrument; for samples also category=X genre=Y"
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "limits",
      -  "styles",
      -  "recipes",
      -  "presets",
      -  "mtl",
      -  "instrument",
      -  "effects",
      -  "modulation",
      -  "drums",
      -  "loops",
      -  "formats",
      -  "sfx",
      -  "examples",
      -  "errors",
      -  "genres",
      -  "generators",
      -  "not_supported"
      -]New value: +[
      +  "limits",
      +  "styles",
      +  "recipes",
      +  "presets",
      +  "mtl",
      +  "instrument",
      +  "effects",
      +  "modulation",
      +  "drums",
      +  "loops",
      +  "formats",
      +  "sfx",
      +  "examples",
      +  "errors",
      +  "genres",
      +  "generators",
      +  "samples",
      +  "not_supported"
      +]
  16. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"Schema 90ddc268"
  17. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is fully covered. The description adds genuine context beyond that: the no-argument index contents, the 256 KB song-text ceiling, and the ~8-minute audio limit with WAV vs Ogg/Opus tradeoffs. It stops short of describing the response shape or how long a returned section can be, which matters with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The trigger and argument ladder are front-loaded, which is good, but the sentence is a long run-on and the 25-topic list simply restates the schema enum, which is duplication rather than added meaning. Trailing tokens ('Tool list 1.6.1. Schema a964948f.') are pure noise for tool selection.

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?

The core discovery workflow (index → topic → q drill-down) is fully explained, which is the main thing an agent needs. But with seven optional parameters, no output schema and a tool that returns potentially long text, the undefined limit/cursor/detail leave a real hole in how to navigate large results.

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 coverage is only 43%, and the description compensates for topic, q, genre and category by explaining their interactions (q narrows to presets and the sample library; q with topic='syntax' selects a syntax section or field). However, limit, cursor and detail receive no explanation in either place, so an agent cannot infer pagination or verbosity behavior.

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 states the tool returns usage notes and documentation for Moose Tracker, and enumerates the sections it can open (syntax, limits, formats, presets, etc.), so the resource is concrete. The verb phrase 'returns usage notes' is soft, and nothing explicitly contrasts it with siblings like sfx or song, but the informational nature is unmistakable.

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?

It gives explicit trigger conditions ('when the user asks for a sound effect... or mentions Moose Tracker') and then spells out the invocation ladder: no args for the index, topic for one section, q for search, topic='syntax' plus q for a syntax field. What is missing is a caution that this is the learn/help path rather than the do-the-work path, so an agent could plausibly confuse 'user asks for a sound effect' with the sfx sibling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources