Skip to main content
Glama
Sign In
Suno MCP Server

Suno MCP Server

by GenCreator-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

match_top_patterns

Find pattern cards and library entries that match a free-text query, helping you reuse proven prompt structures for music generation.

Instructions

Find similar high-rated pattern cards and library entries for a free-text query.

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": {
      "query": "<query>"
    },
    "name": "match_top_patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose that results are restricted to 'high-rated' items, which is genuine behavioral context, but says nothing about ranking, result count behavior, or latency/limits.

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 front-loaded sentence with no filler, but the extreme brevity is under-specification rather than true efficiency for a tool with an undocumented schema.

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?

With no annotations, no output schema, and 0% parameter coverage, the description leaves key gaps: how many results come back, how matches are ranked, and what 'pattern cards' versus 'library entries' means in the result set.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It covers only the 'query' parameter implicitly ('free-text query') and gives no hint about the 'limit' parameter's default of 3 or maximum of 10.

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?

States a specific verb ('Find similar') and resource ('high-rated pattern cards and library entries') with the input mode ('free-text query'). An agent knows what the tool returns, but the description never contrasts it with plausible siblings like suggest_keywords or analyze_intent.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. The phrase 'for a free-text query' weakly implies the input condition, but nothing tells an agent how to choose between this and the other five pattern/music tools.

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

Deploy Server

Other Tools