Skip to main content
Glama

Get Related Skills

get_related_skills
Read-onlyIdempotent

Find skills related to a given skill ID through the Lightcast Skills API, returning related skills rather than similarity scores. Use it to explore adjacent skills for career analysis.

Instructions

Find related skills using the Skills API. Results are related skills, not scored Similarity mappings.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
versionNolatest
skill_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description's only additional claim concerns the shape of the returned results — which the output schema already governs — and says nothing about ordering, pagination via limit/version, or behavior when a skill has no relations.

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?

Only two short sentences, so there is no bloat, and the core action is front-loaded. But the second sentence is a negative clause about a different concept that consumes half the real estate while the parameters and "related" semantics go unexplained — brevity here reads as under-specification rather than economy.

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 an output schema and full annotations, the definition does not need to explain returns or safety. It still needs to explain what relation type it returns and how skill_id/version/limit behave, and neither appears, leaving an agent unable to set version or predict result quality.

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 0% across three parameters (skill_id, version, limit), and the description supplies no compensating meaning: it never mentions that skill_id is required, what version selects ("latest"), or that limit caps result count. The one parameter that determines whether the call succeeds at all is undocumented in prose.

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?

States a verb and resource ("Find related skills") and cites the underlying Skills API, but "related" is never defined — it could mean co-occurrence, hierarchy, or shared taxonomy — and the only distinguishing claim is a negative one about "scored Similarity mappings." An agent can guess this differs from find_similar_skills, but not on what basis.

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 when-to-use statement, no prerequisites, and no named alternative. The phrase "not scored Similarity mappings" gestures at a sibling concept but never says which tool produces those mappings or when to prefer one over the other, leaving the choice entirely to inference.

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