Orca MCP

person_watch_path

Read-onlyIdempotent

Where to start with an actor/director/crew member: one starter pick (safest first watch), best-rated, most popular and recent titles. With region, headline picks also show subscription streaming. Use for 'where do I start with X' questions.

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": {
      "query": "<query>"
    },
    "name": "person_watch_path"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Titles per list, 1-10 (default 3).
`query`	Yes	Person name, e.g. 'nolan' (required).
`region`	No	Optional two-letter country code, e.g. US - adds streaming to headline picks.
`language`	No	ISO language like en-US or fa-IR.	en-US

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful behavioral context: the tool returns multiple ranked lists and that region changes output by adding subscription streaming. It does not contradict the annotations.

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?

The description is concise and front-loads the core purpose, then adds the region-dependent streaming detail and the intended use case. Minor terminology like 'headline picks' is a little vague but does not waste space or obscure the main message.

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?

For a tool with no output schema, the description conveys the shape of the response: multiple title lists and conditional streaming info. It covers the main decision factors (person and region) and the intended use case. It could define 'headline picks' more precisely, but the overall picture is sufficient for correct invocation.

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 coverage is 100%, so the schema already documents all parameters. The description adds some meaning around query (a person) and region (streaming enrichment), but this is mostly redundant with the schema and does not substantially deepen parameter understanding.

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?

States a specific purpose: recommending a starting point for an actor/director/crew member via multiple curated lists (starter pick, best-rated, most popular, recent). The explicit 'Use for where do I start with X' phrase makes the tool's intent unmistakable and distinguishes it from search or detail siblings.

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?

Provides clear usage context with 'Use for where do I start with X' questionsholistically. It does not explicitly name alternative tools or when-not-to-use conditions, but the intended scenario is concrete enough for an agent to select it.

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

All Orca MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?