Skip to main content
Glama
Sign In
mcp-lightcast

mcp-lightcast

by lawwu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Titles Metadata

get_titles_metadata
Read-onlyIdempotent

Retrieve the current Titles taxonomy version and available fields to check schema compatibility or plan title data queries.

Instructions

Discover the current Titles taxonomy version and available fields.

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_titles_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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds only that the call reports a version and a field listing; it says nothing about whether 'latest' resolves dynamically, caching, or result stability across calls, which is the kind of context that would actually help here.

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?

One short, front-loaded sentence with no wasted wording. Its brevity is appropriate for a simple introspection call, though the same sentence could have absorbed the version-parameter hint at no cost to length.

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?

The tool is simple (one optional parameter), an output schema exists to describe return values, and annotations cover safety, so the description roughly meets the bar. What is missing is the meaning of the version argument and any signal about how this metadata relates to the retrieval/search siblings.

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 must carry the single 'version' parameter, and it does not. It never explains what values are accepted, what the default 'latest' resolves to, or whether a historical version can be requested — an agent has to guess based on the word 'current'.

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?

States a specific verb ('Discover') and resource ('Titles taxonomy version and available fields'), which pins it to the Titles taxonomy rather than the many other *_metadata siblings. It stops short of explicitly contrasting itself with get_classification_metadata or get_benchmark_metadata, but the resource naming does the disambiguation work.

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 mention of alternatives. The likely intent — call this before browsing titles to learn the current version and field set — must be inferred entirely from the phrasing 'Discover the current ... version and available fields'.

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