Skip to main content
Glama
Sign In
mcp-lightcast

mcp-lightcast

by lawwu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Skills Metadata

get_skills_metadata
Read-onlyIdempotent

Retrieve Skills taxonomy metadata, including version, supported fields, and skill types, to validate available skill data before querying or integrating Lightcast APIs.

Instructions

Discover the Skills taxonomy version, supported fields, and skill types.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_skills_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNolatest

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety and side-effect profile is fully covered structurally. The description adds that the payload concerns taxonomy version, supported fields and skill types, but given an output schema exists it need not describe the return shape. Value added beyond structured fields is modest.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler and the key output concepts listed in order of likely use. Nothing could be removed without losing information.

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?

Rich annotations and an output schema mean the description need not explain safety or return values, but with an undocumented optional parameter at 0% schema coverage it should have spent a clause on 'version'. Otherwise it is complete for a simple metadata lookup tool.

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?

There is one optional parameter, 'version', defaulting to 'latest', and schema description coverage is 0%, so the schema provides no meaning. The description mentions 'taxonomy version' in passing but never explains that a version can be requested, what valid values look like, or what happens when omitted. This is the definition's weakest area.

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 uses a specific verb ('Discover') paired with concrete resources: taxonomy version, supported fields, and skill types. This clearly separates it from siblings like get_skill_details or search_skills, which operate on individual skills rather than taxonomy metadata. It stops short of explicitly naming a sibling, but the resource is distinctive enough.

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?

No explicit when-to-use statement or named alternative is given; the guidance is only implied by the word 'Discover' and the metadata framing, suggesting it is a first-step introspection call. An agent can infer this is the place to learn valid field names and skill type values before other calls, but the description never says so.

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