Skip to main content
Glama
Sign In

Public Domain Check

by io.github.chomkaevan
OverviewDiscussionsAdmin

Check US public-domain status (full detail)

check_public_domain_full
Read-only

Same check as check_public_domain, but with the complete reasoning, every matching registration and renewal record, and all caveats. Use when you must show your work, cite sources in detail, or audit the decision. Costs $0.02 (x402, USDC on Base).

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": {
      "title": "<title>"
    },
    "name": "check_public_domain_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoKind of work (default book)
yearNoYear of first publication; inferred for 1923–1977 books when omitted
titleYesTitle of the work
authorNoAuthor, composer or creator (improves matching)
originNoCountry of first publication
countriesNoAlso answer for other countries: comma-separated uk, eu, canada, australia, japan, china, india, or all. Same price.
work_for_hireNo
author_death_yearNoFor works published 1978 or later

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / countries
      Added value: +{
+  "description": "Also answer for other countries: comma-separated uk, eu, canada, australia, japan, china, india, or all. Same price.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint=false, the description discloses the pricing model and payment rail: $0.02 via x402, USDC on Base. It also describes the enriched output behavior, including complete reasoning, all matching registration and renewal records, and all caveats. These are material behavioral details an agent needs before invoking a paid tool.

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?

Three sentences, front-loaded with the comparison to check_public_domain, then the use case, then the cost. Every sentence adds distinct information: differentiation, invocation guidance, and payment details. No redundant or filler wording.

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

Completeness5/5

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

With no output schema, the description still explains the return-value richness: complete reasoning, every matching record, and all caveats. Combined with the 88%-covered input schema and explicit pricing, an agent has enough context to decide whether and how to call this tool. No critical gap remains for a read-only paid lookup.

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 high at 88%, so the schema already documents the eight parameters, including enums, defaults, and inferred-year behavior. The description adds no parameter-specific semantics beyond saying it is the same check as check_public_domain. Baseline 3 is appropriate when the schema carries parameter meaning.

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 states a specific check and distinguishes it directly from the sibling check_public_domain: same underlying check, but with complete reasoning, every matching registration and renewal record, and all caveats. The title reinforces the US public-domain scope. An agent can tell exactly what this tool returns versus the basic sibling.

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 gives clear when-to-use guidance: 'Use when you must show your work, cite sources in detail, or audit the decision.' The first sentence contrasts it with check_public_domain, implying the sibling is the simpler alternative. It stops short of an explicit when-not-to-use statement, so it is strong but not fully exhaustive.

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

All Public Domain Check toolsInspect
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