Skip to main content
Glama

Theaudiodb

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. Description adds value by stating scope (by identifier), persistence (authenticated vs anonymous), and time limit (24 hours). Does not contradict 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?

Four sentences, each serving a purpose: purpose, usage, scope/persistence, pairing. No redundancy; highly efficient.

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

Completeness5/5

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

With only 2 string params, no output schema, and no enums, description provides all necessary context: when to use, data scope, durability, and related tools. Fully adequate.

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?

Schema covers 100% of parameters with descriptions. Description adds concrete examples (e.g., 'subject_property') and clarifies the value type (any text), enriching the schema. Slight improvement over baseline 3.

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?

Verb 'Save' + resource 'data' + reuse context. Description explicitly states the tool stores key-value pairs for future use, and mentions sibling tools recall and forget for retrieval and deletion, clearly differentiating from them.

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

Usage Guidelines5/5

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

States when to use: 'when you discover something worth carrying forward'. Mentions pairing with recall and forget. Provides explicit context for usage within conversations or across sessions.

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

All Theaudiodb toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

Most tools have clearly distinct purposes and detailed descriptions, but ask_pipeworx and ask_pipeworx_beta are currently identical, and several data-answer/prediction-market tools overlap in intent. The music tools are generally separable once name-vs-ID and album-vs-track distinctions are recognized.

Naming Consistency4/5

The vast majority of tools follow lowercase snake_case with a verb-first or domain-prefixed pattern (search_artist, get_album_tracks, validate_claim, polymarket_edges). Minor deviations like remember/recall/forget and recent_alerts/recent_changes break the pattern slightly but do not create real confusion.

Tool Count1/5

35 tools is far too many for a server named TheAudioDB, and only 4 of them are actually music-metadata tools. The remaining 31 tools form an unrelated Pipeworx/Polymarket data-research platform, which is an extreme scope mismatch rather than a modest overage.

Completeness2/5

The music-metadata surface covers artist search, album search, artist-by-ID, and album tracks, but there is no track search, no album-by-ID getter, and no general track lookup, so common music queries will dead-end. The unrelated Pipeworx side is broad, but for a server presented as TheAudioDB the domain coverage has significant gaps.

Resources