Frinkiac

Random

random

Read-onlyIdempotent

Random screencap + its caption.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`show`	No

Output Schema

TableJSON Schema

Name	Required	Description
`raw`	Yes	Raw API response object
`show`	Yes	The show queried
`caption`	Yes	Caption text joined from subtitles
`episode`	No	Episode key (e.g. S05E15) or null if unavailable
`frame_url`	No	URL to the screencap image or null if episode/timestamp unavailable
`timestamp`	No	Frame timestamp in milliseconds or null if unavailable

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "show": "simpsons"
+  },
+  {
+    "show": "futurama"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "caption": {
+      "description": "Caption text joined from subtitles",
+      "type": "string"
+    },
+    "episode": {
+      "description": "Episode key (e.g. S05E15) or null if unavailable",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "frame_url": {
+      "description": "URL to the screencap image or null if episode/timestamp unavailable",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "raw": {
+      "description": "Raw API response object",
+      "type": "object"
+    },
+    "show": {
+      "description": "The show queried",
+      "type": "string"
+    },
+    "timestamp": {
+      "description": "Frame timestamp in milliseconds or null if unavailable",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "show",
+    "caption",
+    "raw"
+  ],
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already indicate readOnlyHint, idempotentHint, etc. The description adds no extra behavioral context beyond the obvious.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short and front-loaded, but lacks structure or additional detail that would justify its brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description does not need to explain returns, but it fails to explain the input parameter or provide usage patterns, making it incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the 'show' parameter or its allowed values. This leaves the agent with no guidance on how to use the parameter.

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

Purpose4/5

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

The description clearly states it returns a random screencap and its caption. However, it does not distinguish from sibling tools like 'caption' or specify the source beyond examples.

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

Usage Guidelines2/5

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

No guidance on when to use this tool or alternatives. The description is too brief to provide context for appropriate use.

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

All Frinkiac tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.