New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_ttab_document

Retrieve and read one specific TTABVUE filing by proceeding number and entry number. Returns filing metadata, a working USPTO TTABVUE viewer link, direct PDF link when available, extraction/readability status, document text, and optional query-centered excerpts. Use get_ttab_proceeding_details fi...

SERVERGleanMark Trademark Search SOURCEhttps://gleanmark.com/mcp
Low RISK CLASS
Category Read
Parameters 42 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-gleanmark-trademark-search/get-ttab-document.md

What get_ttab_document does on GleanMark Trademark Search

AI agents call get_ttab_document to retrieve information from GleanMark Trademark Search without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
max_chars integer
text_query string Optional word or phrase; returns up to five excerpts centered on matches.
entry_number integer Yes TTABVUE entry number returned by get_ttab_proceeding_details.
proceeding_number string Yes Seven- or eight-digit TTAB proceeding number.

Parameters from the server's own tool schema.

Why get_ttab_document is rated Low

This tool performs a straightforward data retrieval operation on public trademark records. It queries a database by proceeding and entry number and returns document information and text. There are no side effects, no code execution, no data modification, and no financial impact. This is a classic Read operation appropriate for a legal research context where accessing public trademark proceedings is routine and safe.

From the tool's definition The tool description explicitly states it 'Retrieve[s] and read[s]' a TTAB filing and 'Returns filing metadata...document text' - core retrieval operations with no modification, deletion, or execution capabilities.

Questions about get_ttab_document

What does the get_ttab_document tool do? +

Retrieve and read one specific TTABVUE filing by proceeding number and entry number. Returns filing metadata, a working USPTO TTABVUE viewer link, direct PDF link when available, extraction/readability status, document text, and optional query-centered excerpts. Use get_ttab_proceeding_details first when the entry number is unknown. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.

What parameters does get_ttab_document accept? +

get_ttab_document accepts 4 parameters: max_chars, text_query, entry_number, proceeding_number. Required: entry_number, proceeding_number. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_ttab_document? +

Register the GleanMark Trademark Search MCP server in PolicyLayer and add a rule for get_ttab_document: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches GleanMark Trademark Search. Nothing to install.

What risk level is get_ttab_document? +

get_ttab_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_ttab_document? +

Yes. Add a rate_limit block to the get_ttab_document rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block get_ttab_document completely? +

Set action: deny in the PolicyLayer policy for get_ttab_document. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides get_ttab_document? +

get_ttab_document is provided by the GleanMark Trademark Search MCP server (https://gleanmark.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GleanMark Trademark Search, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GleanMark Trademark Search's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.