Skip to main content
Glama

Get one film MCP server

get_film_mcp
Read-onlyIdempotent

Get the full mcp.film entry for one server by slug: description, install commands, auth requirements, sample tools, links, field notes (caveats), and machine-checked evidence (evidence level, last_probe of the hosted endpoint, package_check).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_film_mcp"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesServer slug, e.g. 'martini' or 'elevenlabs'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a safe, idempotent read operation. The description adds useful behavioral context by enumerating the returned data, including machine-checked evidence fields like evidence level, last_probe, and package_check, though it omits what happens when a slug is not found.

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 description is a single dense but well-structured sentence. The core action is front-loaded, and the returned fields are listed efficiently with no filler.

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?

With only one parameter and a fully described schema, the description provides a clear inventory of what the returned entry contains. It does not explain error behavior for an invalid slug, but for a simple read-only lookup the definition is nearly complete.

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%, and the schema itself gives the slug format with examples. The description only confirms retrieval by slug, adding no further semantics beyond the structured field, so the baseline of 3 is appropriate.

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?

The description uses a specific verb-resource pair: get the full mcp.film entry for one server by slug. It clearly distinguishes this single-entry lookup from sibling tools like search_film_mcps and list_film_categories by emphasizing one server identified by slug.

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?

The phrase 'by slug' clearly signals when to use this tool: when the server slug is already known. It does not explicitly contrast this with search_film_mcps or list tools, but the context is strong enough to guide selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.