Skip to main content
Glama
Sign In
mcp-lightcast

mcp-lightcast

by lawwu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Classification Metadata

get_classification_metadata
Read-onlyIdempotent

Retrieves source types for an active classifier release; set version to latest to discover the newest nonexpired release.

Instructions

Get source types for an active classifier release. latest discovers the newest nonexpired release.

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_classification_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNolatest

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description adds useful behavior beyond them: 'latest' resolves to the newest nonexpired release, which is a real resolution rule an agent cannot read off the annotations. It stops short of saying what happens when no active release exists or when a supplied version is expired/invalid.

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?

Two short sentences, front-loaded with the capability and followed immediately by the default-value rule. No filler, no restatement of the tool name, and every clause adds information.

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?

This is a low-complexity tool: zero required parameters, one optional string, and an output schema that already documents the return shape, so the description needn't explain results. It covers what is fetched and the meaning of the default; only the accepted format of an explicit version and the empty/expired-release case are left open.

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

Parameters3/5

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

Schema description coverage is 0% for the single 'version' parameter, so the description has to carry meaning, and it does partially by defining the 'latest' default as the newest nonexpired release. However, it never states what an explicit version value should look like (a release identifier? a date? a number?) or what the accepted set is.

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 concrete verb ('Get') and a concrete payload ('source types') scoped to an active classifier release, which is more informative than the bare title. It does not explicitly differentiate itself from the nearest sibling, list_classification_releases, though the mention of an 'active classifier release' hints at the relationship.

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 only implied: the reader infers this is the call to make when metadata about a classifier release's sources is needed, and that 'latest' is the default choice. There is no explicit statement of when to prefer this over list_classification_releases or the other *_metadata siblings, and no prerequisites or failure conditions are given.

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