Skip to main content
Glama

Find Similar Skills

find_similar_skills
Read-onlyIdempotent

Finds scored skills similar to a given skill ID so you can compare related skills and set a result limit.

Instructions

Find scored similar skills. Requires the separate Similarity API subscription.

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": {
      "skill_id": "<skill_id>"
    },
    "name": "find_similar_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
skill_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety bar is low. The description's one added fact, the subscription requirement, is genuinely useful access context, but it says nothing about how results are scored, ordered, or truncated beyond the schema default.

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 tight sentences, front-loaded with the action and followed by the access caveat. Nothing is redundant, though the brevity borders on under-specification rather than economy.

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?

An output schema and rich annotations remove the need to describe return values or safety. Still missing are the seed-parameter meaning, what "scored" implies for ordering, and any routing hint versus get_related_skills, which matters for a two-param tool with zero schema descriptions.

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 carries the burden for skill_id and limit, yet it explains neither. "Similar skills" weakly implies skill_id is the seed skill, but the meaning and behavior of limit (default 10, max 100) is left entirely to structural constraints.

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?

"Find scored similar skills" gives a verb and resource plus a qualifier (scored), so the basic action is clear. But it never distinguishes this from the sibling get_related_skills, leaving an agent unsure which similarity endpoint to pick.

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?

The only conditional statement is an entitlement requirement (Separate Similarity API subscription), which is a prerequisite, not usage guidance. There is no when-to-use, when-not-to-use, or named alternative.

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