get_cohort_event_intervals
Aggregate event-to-event pendency across a COHORT of marks — e.g. "average days from office action to publication for marks published in Q2 2026". Pick the cohort by an anchor event (preset: publication, notice_of_publication, registration, notice_of_allowance, abandonment, first_office_action — ...
This record as markdown: /tools/com-gleanmark-trademark-search/get-cohort-event-intervals.md
What get_cohort_event_intervals does on GleanMark Trademark Search
AI agents call get_cohort_event_intervals 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
end_event | string | — | Interval end event (first occurrence on/after the start event). Defaults to the cohort event itself. |
max_sample | integer | — | Max cohort marks to measure (default 1000, max 2000). |
start_event | string | — | Interval start event (first occurrence on/before the cohort event). Defaults to first_office_action. |
cohort_event | string | — | Preset anchor event defining cohort membership (e.g. publication = PUBO). |
cohort_date_to | string | Yes | Cohort window end (YYYY-MM-DD). Required. Window max 366 days. |
end_event_codes | array | — | Alternative to end_event: raw event codes (trailing * = prefix). |
cohort_date_from | string | Yes | Cohort window start (YYYY-MM-DD). Required. |
start_event_codes | array | — | Alternative to start_event: raw event codes (trailing * = prefix). |
cohort_event_codes | array | — | Alternative to cohort_event: raw USPTO event codes; trailing * matches a prefix (e.g. "NPUB*"). |
Parameters from the server's own tool schema.
Why get_cohort_event_intervals is rated Low
This tool retrieves and queries trademark prosecution data to generate statistical insights. It operates purely on read operations against the USPTO trademark database—selecting cohorts, filtering by date ranges, and computing aggregate metrics. The tool does not create, modify, delete, or execute arbitrary code.
From the tool's definition Tool aggregates and analyzes historical trademark event data within specified date windows, returning statistics (average, median, percentiles) and example marks.
Attacks that exploit this kind of access
The rule that runs get_cohort_event_intervals safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GleanMark Trademark Search, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_cohort_event_intervals, this is the rule to start with:
get_cohort_event_intervals is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GleanMark Trademark Search, apply this rule, and every get_cohort_event_intervals call is checked against it from then on.
Questions about get_cohort_event_intervals
Aggregate event-to-event pendency across a COHORT of marks — e.g. "average days from office action to publication for marks published in Q2 2026". Pick the cohort by an anchor event (preset: publication, notice_of_publication, registration, notice_of_allowance, abandonment, first_office_action — or raw event codes, trailing * = prefix) within a date window (max 366 days), and an interval start/end event. Returns avg/median/percentiles in days, how many cohort marks never had the start event, and example marks. Samples up to max_sample marks from the start of the window and says so when truncated. Use get_event_code_reference first if you need non-preset event codes. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
get_cohort_event_intervals accepts 9 parameters: end_event, max_sample, start_event, cohort_event, cohort_date_to, end_event_codes, cohort_date_from, start_event_codes, cohort_event_codes. Required: cohort_date_to, cohort_date_from. The full parameter table on this page comes from the server's own tool schema.
Register the GleanMark Trademark Search MCP server in PolicyLayer and add a rule for get_cohort_event_intervals: 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.
get_cohort_event_intervals is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_cohort_event_intervals 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.
Set action: deny in the PolicyLayer policy for get_cohort_event_intervals. 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.
get_cohort_event_intervals 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.
This server
Across the catalogue