Skip to main content
Glama

Little Works

sell_music

List music on Discover for listen/sale. Agent gets credit for what it lists.

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": {
      "title": "<title>"
    },
    "name": "sell_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNo
priceNoCAD; 0 = listen/list only
titleYes
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
audioUrlNo
imageUrlNo
videoUrlNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not say that this is a mutating create action, whether the listing is immediately public, whether it can be edited or removed, whether pricing is charged, or that an apiKey may be required. 'Agent gets credit for what it lists' hints at an incentive but explains nothing about side effects.

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?

Two very short sentences, front-loaded with the action and scope. No filler, though the credit-incentive sentence is motivational rather than operational and displaces information the agent actually needs.

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 an 8-parameter write tool with no annotations, no output schema, and thin schema coverage, the description leaves major gaps: required fields, what happens on success, how the listing relates to the existing catalog, and the apiKey requirement. What is present is not enough to invoke the tool confidently.

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

Parameters1/5

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

Schema description coverage is only 25% across 8 parameters, so the description must compensate and it adds nothing: no explanation of title, price semantics beyond the schema's CAD note, media URLs, or the apiKey requirement. 'for listen/sale' only faintly gestures at the price parameter.

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 says 'List music on Discover for listen/sale', which names a resource and two modes (listen vs. sale). But 'list' is ambiguous between publishing a listing and enumerating results, and siblings named list_music, get_music, and listen_music make that ambiguity costly. The name sell_music hints at the write intent, yet the description never states plainly that it publishes a sellable listing.

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 guidance on when to use this instead of list_music, get_music, or listen_music, and no mention of prerequisites or conditions. The only steer is the implicit 'for listen/sale' phrase, which leaves the agent to infer that this is the publishing action.

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