suede-skills-mcp

Search Suede Skills

search_suede_skills

Read-onlyIdempotent

Rank Suede skills against a task description to find the best-matching routes, with optional area and specialty filters.

Instructions

Rank Suede skills against a task description and return the best-matching routes.

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": "search_suede_skills"
  }
}

Input Schema

Name	Required	Description
`area`	No	Optional area filter.
`limit`	No	Maximum matches to return, up to 25.
`query`	Yes	Task, problem, or intent to route.
`specialty`	No	Optional specialty filter: ship, craft, found, demand, revenue, position.

Output Schema

Name	Required	Description	Default
`query`	Yes
`matches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds the useful behavioral fact that results are relevance-ranked ("best-matching"), but says nothing about scoring, threshold behavior, or what happens when nothing matches.

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 sentence with no filler, and the action and result are front-loaded. It is arguably over-compressed for a four-parameter routing tool, but nothing is wasted.

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

Completeness4/5

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

With an output schema present and full schema description coverage, the description only needs to establish purpose and selection context, which it largely does. The remaining gap is guidance on choosing this over the sibling list/get tools.

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 coverage is 100% with enum values and min/max bounds documented for every parameter, so the schema carries the load and the baseline is 3. The description adds a small amount by framing query as a task/problem/intent to be routed. This clears the baseline slightly.

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 description names a specific verb and resource ("Rank Suede skills") plus the input ("against a task description") and output ("best-matching routes"), which is enough to distinguish it from get_suede_skill or list_suede_skills by implication. It stops short of explicitly contrasting itself with those siblings by name.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: "rank ... against a task description" signals this is for task-to-skill routing, not enumeration. There is no explicit when/when-not guidance and no pointer to list_suede_skills for browsing the full catalog instead.

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

Deploy Server