Skip to main content
Glama

List intent-routed recommendations

list_film_recommendations
Read-onlyIdempotent

List mcp.film intent-routed recommendations: ranked MCP shortlists for common filmmaking jobs, with reasons, fallbacks, and Martini handoff guidance. Use get_film_recommendation for full detail.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1-100. Default 20.
queryNoOptional free-text search over titles, summaries, best_for text, tags, server names, and Martini handoff guidance.
offsetNoStart index for paging; use next_offset from the previous call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Page size, 1-100. Default 20.",
      +  "type": "number"
      +}
    • 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.3/5.0
Behavior4/5

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

The annotations already declare a safe, idempotent read with no destructive or open-world side effects. The description adds useful behavioral context by stating the return content includes reasons, fallbacks, and Martini handoff guidance, though it does not discuss pagination or rate limits (which the schema's offset/limit fields partly cover).

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 tight sentences: the first front-loads the purpose and content, the second gives the routing alternative. No wasted words.

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?

With annotations covering safety, schema documenting all three parameters, and the description explaining the returned content, an agent has enough to invoke correctly. The absence of an output schema is compensated by the description's mention of reasons, fallbacks, and handoff guidance.

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 the baseline is 3; the description does not mention limit, query, or offset, leaving their semantics entirely to the schema. No additional meaning is added beyond structured fields.

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 states a concrete verb ('List') and a well-scoped resource ('mcp.film intent-routed recommendations'), then elaborates what the list contains ('ranked MCP shortlists for common filmmaking jobs, with reasons, fallbacks, and Martini handoff guidance'). It also explicitly distinguishes itself from get_film_recommendation, so an agent can route correctly without opening the 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?

It names get_film_recommendation as the alternative for full detail, giving clear context for choosing between summary and detail. It stops short of enumerating when-not-to-use or comparing against every sibling such as recommend_film_mcps, so a 4 rather than a 5.

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.