Skip to main content
Glama

harmony grade

harmony-grade
Read-onlyIdempotent

Color grade derived from harmony/tonal center (Scriabin CoF<->color, prisms.db) 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": "harmony-grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
featuresYesobject{tension,harmony,pitch}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 openWorldHint=true, so safety and determinism are covered structurally. The description adds genuinely useful non-schema context: the call is paid ($0.05 via x402 on Base), which matters for cost-aware selection, and that data comes from prisms.db (consistent with openWorldHint). It does not describe the shape of the returned 'grade' (hex value, name, enum) or any failure/rate-limit behavior.

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?

It is short and front-loads the domain explanation before the pricing, which is a reasonable order. But it is a sentence fragment with a parenthetical of internal jargon (Scriabin CoF<->color, prisms.db) and a tacked-on price clause, so structure is functional rather than clean.

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?

For a paid, open-world tool with a nested required object and no output schema, the description leaves key gaps: what a 'color grade' actually is and its format, what the three feature fields represent (type/range), and whether the result depends on external DB state. Payment disclosure is a plus, but not enough to call it complete.

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 reported at 100% and there is only one parameter, so the baseline is 3. The schema entry is a bare nested object sketch ('object{tension,harmony,pitch}') with no types, ranges, or units, and the description adds no field-level meaning — the nested structure is where an agent would most need help.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a niche domain operation (deriving a color grade from a harmonic/tonal center using a Scriabin circle-of-fifths mapping and prisms.db), which is more specific than the title alone. However, it is a noun phrase with no verb, and 'color grade' is ambiguous — it could be an image treatment, a score, or a color assignment. It does not clearly distinguish itself from a sibling like synesthetic-av, which plausibly overlaps.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The only implicit signal is that the tool operates on harmony/tonal-center data, which weakly implies it applies when such features are available, but an agent must infer all invocation conditions.

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