FilmRightsProof

Search public copyright records

filmrightsproof.search_public_records

Read-onlyIdempotent

Search likely U.S. Copyright Office public records for a film, television, or underlying creative work. Use this free bounded search to identify candidate works before specialist reconciliation; it does not build the paid rights dossier.

Input Schema

TableJSON Schema

Name	Required	Description
`year`	No	Optional release, publication, creation, or registration year used to narrow candidate matches.
`limit`	No	Maximum number of candidate public-record matches to return or inspect.
`title`	Yes	Film, television, or underlying creative-work title to search in U.S. Copyright Office public records.
`creator`	No	Optional creator, author, writer, director, producer, or other credited name used to disambiguate similarly titled works.
`workType`	No	Optional work-type hint, such as motion picture, television, screenplay, book, or other underlying creative work.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`coverage`	Yes
`freshness`	Yes
`candidates`	Yes
`legalNotice`	Yes
`evidenceGaps`	Yes
`schemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 13, 2026

addedInput schema / properties / creator / description

Added value: +"Optional creator, author, writer, director, producer, or other credited name used to disambiguate similarly titled works."

addedInput schema / properties / limit / description

Added value: +"Maximum number of candidate public-record matches to return or inspect."

addedInput schema / properties / title / description

Added value: +"Film, television, or underlying creative-work title to search in U.S. Copyright Office public records."

addedInput schema / properties / workType / description

Added value: +"Optional work-type hint, such as motion picture, television, screenplay, book, or other underlying creative work."

addedInput schema / properties / year / description

Added value: +"Optional release, publication, creation, or registration year used to narrow candidate matches."

Changed1 schema field changedSep 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "candidates": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "publicationYear": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "reasons": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "registrationNumber": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "score": {
+            "type": "number"
+          },
+          "title": {
+            "type": "string"
+          },
+          "workType": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "title"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "coverage": {
+      "type": "object"
+    },
+    "evidenceGaps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "freshness": {
+      "additionalProperties": true,
+      "properties": {
+        "currentEvidenceUsable": {
+          "type": "boolean"
+        },
+        "currentLookupAttempted": {
+          "type": "boolean"
+        },
+        "currentLookupVerified": {
+          "description": "Narrow compatibility summary. True only when the bounded current lookup completed without normalization rejection; it does not mean exhaustive coverage.",
+          "type": "boolean"
+        },
+        "error": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "evidenceStatus": {
+          "enum": [
+            "usable",
+            "usable_no_qualifying_match",
+            "partial",
+            "partial_no_qualifying_match",
+            "zero_hits",
+            "normalization_failed",
+            "unavailable"
+          ]
+        },
+        "fallback": {
+          "type": "object"
+        },
+        "observation": {
+          "type": "object"
+        },
+        "observedAt": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "parsingStatus": {
+          "enum": [
+            "succeeded",
+            "failed",
+            "not_completed",
+            "not_attempted"
+          ]
+        },
+        "queryCompletedAt": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "queryStartedAt": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "schemaVersion": {
+          "const": "filmrightsproof-freshness.v2"
+        },
+        "searchScope": {
+          "anyOf": [
+            {
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "sourceMix": {
+          "type": "object"
+        },
+        "transportStatus": {
+          "enum": [
+            "succeeded",
+            "failed",
+            "not_attempted"
+          ]
+        }
+      },
+      "required": [
+        "schemaVersion",
+        "currentLookupAttempted",
+        "currentLookupVerified",
+        "currentEvidenceUsable",
+        "transportStatus",
+        "parsingStatus",
+        "evidenceStatus",
+        "observation",
+        "fallback"
+      ],
+      "type": "object"
+    },
+    "legalNotice": {
+      "type": "string"
+    },
+    "query": {
+      "type": "object"
+    },
+    "schemaVersion": {
+      "const": "public-record-search.v1"
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "query",
+    "candidates",
+    "coverage",
+    "freshness",
+    "evidenceGaps",
+    "legalNotice"
+  ],
+  "type": "object"
+}

First observedSep 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior, so the safety profile is covered. The description adds useful context beyond that: the search is free and bounded (matching the limit=20 cap) and is not the paid dossier. It does not disclose rate limits or result-order guarantees.

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 sentences, zero filler, purpose front-loaded before the usage constraint. Every clause earns its place.

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 all parameters documented, the description needn't explain return values. It conveys scope, cost, and boundary adequately, though it could say slightly more about how results should be adjudicated.

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 every parameter (title, year, creator, workType, limit) is already documented in the schema. The description adds no per-parameter syntax or format detail, so baseline 3 applies.

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?

States a specific verb (search) and resource (U.S. Copyright Office public records) scoped to film, television, or underlying creative works. It implicitly distinguishes itself from the paid rights path, but never names the sibling filmrightsproof.trace_public_rights directly, so the differentiation remains partial.

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?

Gives a clear context: 'Use this free bounded search to identify candidate works before specialist reconciliation.' The clause 'it does not build the paid rights dossier' signals when-not-to-use. It does not explicitly name the alternative tool, so it stops short of full routing guidance.

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

All FilmRightsProof 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?