Skip to main content
Glama

synesthetic av

synesthetic-av
Read-onlyIdempotent

Audio->visual via formal Scriabin AV-map (pitch->hue, harmony->geometry) Price: $0.05 per call, USDC on Base via x402.

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": {
      "features": "<features>"
    },
    "name": "synesthetic-av"
  }
}

Input Schema

NameRequiredDescriptionDefault
featuresYesobject{pitch,rms,tempo,tension,timbre,harmony}
audio_urlNooptional

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The description adds genuine context the annotations don't carry: a per-call price of $0.05 in USDC on Base via x402, which tells the agent this is a paid, payment-gated call and that a wallet/x402 flow is involved. However, with no output schema it never says what comes back (an image, a JSON hue/geometry map, a URL), leaving the most important behavioral question unanswered.

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

Conciseness4/5

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

A single dense sentence that front-loads the core transformation and appends pricing as secondary information. Nothing is redundant; the only weakness is the telegraphic fragment style, which trades clarity for brevity.

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?

Annotations already cover the safety profile (read-only, idempotent, non-destructive) and the description covers cost, so the essentials for a read-only transform are mostly present. But for a tool with a nested required object, an optional audio_url, and no output schema, the missing return-type description and the unclear relationship between features and audio_url leave a meaningful gap.

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 100%, so the baseline is 3 and the schema already documents 'features' as {pitch,rms,tempo,tension,timbre,harmony} and 'audio_url' as optional. The description's mapping note (pitch->hue, harmony->geometry) adds a little meaning about how two of those fields are used, but it says nothing about when audio_url is expected or what units/ranges the values take.

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 arrow notation 'Audio->visual via formal Scriabin AV-map' states the transformation and the mechanism, with 'pitch->hue, harmony->geometry' making it concrete. It is clearly distinguishable from the crypto-flavored siblings (token-check, wallet-risk, etc.), though it is phrased as a fragment rather than a verb+resource statement.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus when not to, nor any precondition guidance (e.g., that audio features must be pre-extracted). The only implied guidance is that the tool consumes audio-derived features; the agent must infer everything about selection.

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