Skip to main content
Glama

Frinkiac

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search

search
Read-onlyIdempotent

Frinkiac and its sister sites Morbotron and Master of All Science — subtitle search over screencaps of The Simpsons (default), Futurama and Rick and Morty. Give a remembered line of dialogue and each match returns the episode key, frame timestamp, a still-image URL and a GIF URL. Answers which episode and scene a cartoon quote is from, with the screencap or GIF.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
showNosimpsons | futurama | rickandmorty (default simpsons)
limitNo1-100 (default 20)
queryYesQuote / keywords

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
showYesThe show queried (simpsons, futurama, or rickandmorty)
countYesNumber of results returned
resultsYesArray of matching screencaps

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "D'oh!"
+  },
+  {
+    "limit": 10,
+    "query": "eat my shorts",
+    "show": "simpsons"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of results returned",
+      "type": "number"
+    },
+    "results": {
+      "description": "Array of matching screencaps",
+      "items": {
+        "properties": {
+          "Episode": {
+            "description": "Episode key (e.g. S05E15)",
+            "type": "string"
+          },
+          "Id": {
+            "description": "Result ID",
+            "type": "number"
+          },
+          "Timestamp": {
+            "description": "Frame timestamp in milliseconds",
+            "type": "number"
+          },
+          "frame_url": {
+            "description": "URL to the screencap image",
+            "type": "string"
+          },
+          "gif_url": {
+            "description": "URL to a 5-second GIF starting at timestamp",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "show": {
+      "description": "The show queried (simpsons, futurama, or rickandmorty)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "show",
+    "count",
+    "results"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable output details (episode key, timestamp, still/GIF URLs) and clarifies search scope across shows, supplementing the annotation data without contradiction.

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 two sentences with no fluff. The first names the sources and defines the search domain; the second explains input and output format. Every clause contributes to tool understanding.

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 an output schema present and rich annotations, the description adequately covers the search use case, return fields, and default show behavior. It could optionally mention no-match behavior, but the provided information 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 parameter descriptions already define query, show, and limit. The description's 'remembered line' phrasing aligns with the query parameter but adds little beyond the schema. Baseline 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 clearly states the tool searches subtitles across Frinkiac, Morbotron, and Master of All Science, and explains it answers which episode and scene a cartoon quote is from. This specific verb+resource pairing distinguishes it from generic search tools.

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 provides clear context by instructing users to give a remembered line of dialogue and lists the types of results. It does not explicitly name alternatives or exclusions, but the intended use case for cartoon quote lookup is unambiguous.

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

All Frinkiac toolsInspect
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.

Resources