Skip to main content
Glama

List guessit properties

guessit_properties
Read-onlyIdempotent

Lists every movie and TV filename metadata property that parsing can return, with possible enum values and free-form fields, so you can validate output.

Instructions

List every property guessit can return with its possible values (enum values such as source: ["Blu-ray", "Web", ...]; [null] for free-form ones such as title).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.3.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile is covered. The description adds real value beyond them by explaining the shape of the result: enum-backed properties show their candidate values, and free-form ones are marked [null]. That is useful return-shape context, though nothing is said about auth, limits, or size.

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?

The whole definition is one sentence, with the core action first and the illustrative examples kept compact in parentheses. Every clause earns its place, because the examples show how enum and free-form properties differ in the output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only metadata tool with an output schema available, the description covers exactly what an agent needs: what the tool returns and how to read enum versus free-form entries. Nothing else is required before the tool can be invoked correctly.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline score is 4. The input schema is empty with additionalProperties false, and the description correctly introduces no parameter concepts.

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 supplies a specific verb and resource: it lists every property 'guessit' can return along with possible values. That clearly separates it from the parsing siblings guessit and guessit_batch, even though it never names them. It is a clear purpose statement, but it offers no explicit contrast with the sibling tools, so 4 is the right score.

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?

The description implies how the tool is used: discover which properties and values can appear before or after calling the parsing tools. It never states when to prefer it over guessit, and it gives no exclusions. That is implied usage only, so the score is 3.

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