Deprecated: use getFrames with mode: "overview".
| Name | Required | Description | Default |
|---|---|---|---|
| jamId | Yes | Jam identifier — a UUID or a jam.dev URL | |
| intent | No | In 15-30 English words, your larger task and why this call helps it. People by role ("a customer"); no argument values or secrets. | |
| llm_model | No | Your exact model id from your system prompt, or "unknown". Never guess. |
Changes observed during successful MCP inspections.
Input schema / properties / intent / descriptionPrevious value: -"In 15-30 words, say what larger task you are working on and why this tool helps it. Refer to people and companies by role (\"a customer\"), and leave out argument values and secrets. Use English. Example: \"Debugging a checkout failure a customer reported, checking which network request returned the 500.\""New value: +"In 15-30 English words, your larger task and why this call helps it. People by role (\"a customer\"); no argument values or secrets."Input schema / properties / llm_model / descriptionPrevious value: -"The exact model identifier you are running as, from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Pass \"unknown\" if you are not certain; never guess."New value: +"Your exact model id from your system prompt, or \"unknown\". Never guess."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare this tool as read-only, idempotent, non-destructive, and deprecated via the title. The description adds a concrete replacement path, which is useful, but it does not describe other behavioral traits such as what the analysis did or how it behaved before deprecation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no wasted wording. It communicates deprecation and the replacement immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a deprecated redirect tool, the description is nearly complete: it tells the agent not to use this tool and what to use instead. It does not explain the legacy tool's return behavior, but that is a minor gap given the deprecation notice.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all three parameters are already documented in the input schema. The description adds no parameter-specific meaning beyond the schema, which is acceptable given complete schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the tool as deprecated and points to a replacement, which helps distinguish it from getFrames. However, it never states what analyzeVideo itself does beyond what the tool name implies, so the actual purpose remains vague.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives explicit migration guidance: use getFrames with mode "overview" instead. For a deprecated tool, this is exactly the usage instruction an agent needs and leaves little ambiguity about avoiding this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.