FedWatch — Federal Funding & Lien Watcher

ip_search

USPTO trademark/patent data — GATED on credential provisioning: the modern USPTO APIs (ODP, TSDR case status) all require a registered API key (keyless routes retired). The fleet holds a scoped USPTO ODP credential in its secure vault from the USIPE program; copying it into this Worker (secret USPTO_ODP_API_KEY, budgeted against the shared daily cap) is the named unlock. uspto_bulk is the keyless bulk-file path (ETL shape, planned). Calls return the named gate until a source is promoted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ip_search"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum returned records (tier-capped)
`keyword`	No	Trademark/patent keyword (reserved for promoted adapters)
`source_id`	No	Source id: uspto_odp (default) or uspto_bulk

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations the description carries the full burden, and it does disclose meaningful behavior: calls return a 'named gate' until a source is promoted, and usage is 'budgeted against the shared daily cap' (a rate-limit hint). But this is wrapped in ops-facing jargon (vault, Worker, USIPE program, secret name) and says nothing about what a successful search returns.

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

Conciseness2/5

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

The text is bloated with internal infrastructure detail ('scoped USPTO ODP credential in its secure vault from the USIPE program', the secret's name) that is low-value for an agent selecting a tool. The essential fact — the tool is gated and won't return data yet — is buried rather than front-loaded.

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

Completeness3/5

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

For a low-complexity, zero-required-param tool with full schema coverage and no output schema, the description conveys the crucial gating state. It still leaves the actual search behavior and any success-path result shape unexplained.

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 schema already documents limit, keyword, and source_id. The description adds no syntax or format meaning beyond the schema, so baseline 3 applies.

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

Purpose3/5

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

The resource is specific ('USPTO trademark/patent data'), which does distinguish it from the domain-search siblings, but the description never states the operation itself (search by keyword) — most of the text is about credential provisioning and gating rather than what the tool does when it works.

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

Usage Guidelines3/5

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

It names an alternative path ('uspto_bulk is the keyless bulk-file path') and implies the tool is gated until a credential is promoted, giving partial routing guidance. However, it never gives a clean 'use this when / don't use this when' rule, and the alternative is described as 'planned,' leaving the agent unsure what to do now.

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

All FedWatch — Federal Funding & Lien Watcher 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?