Skip to main content
Glama
Sign In

mcp.film directory

by film.mcp
OverviewDiscussionsAdmin

List capability tags

list_film_capabilities
Read-onlyIdempotent

List capability tags in the mcp.film registry, ranked by number of matching servers (tag, page url, counts). Paged. Use get_film_capability for the server cluster behind one tag.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1-100. Default 50.
queryNoOptional substring filter, e.g. 'video', 'voice', or 'timeline'.
offsetNoStart index for paging; use next_offset from the previous call.
min_countNoOnly include capability tags with at least this many servers. Default 2 (tags with a published page).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Page size, 1-100. Default 50.",
+  "type": "number"
+}
    • changedInput schema / properties / min_count / description
      Previous value: -"Only include capability tags with at least this many servers. Default 1."New value: +"Only include capability tags with at least this many servers. Default 2 (tags with a published page)."
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Start index for paging; use next_offset from the previous call.",
+  "type": "number"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so credit goes to what the description adds: ranking order (by number of matching servers), pagination behavior, and the shape of returned records. It does not state the registry's update cadence or whether counts are live, but for a read-only listing that is a minor gap.

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?

Three short sentences, verb and scope front-loaded, return fields and the sibling handoff packed without waste. Nothing redundant with the title or schema.

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?

No output schema exists, and the description compensates by enumerating the returned fields (tag, page url, counts) — an important disclosure. Combined with paging and ranking, an agent has enough to call and interpret results; only edge behavior (empty result, max offset) is unstated.

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 100%, so all four parameters are already documented in-schema; the description adds only the concept of paging and ranking-down by count. No additional meaning about how query interacts with ranking or how min_count affects the default page is supplied beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource+scope: 'List capability tags in the mcp.film registry, ranked by number of matching servers', and it even declares the returned fields (tag, page url, counts). It names the sibling get_film_capability and the distinction (cluster behind one tag), so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes to get_film_capability for per-tag detail, which is the main alternative an agent would confuse this with. No when-not-to-use guidance is given (e.g. use search_film_mcps for finding servers directly), but the alternative named is the relevant one for this listing's ambiguity.

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

All mcp.film directory toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources