Skip to main content
Glama

reassign

by app.reassign
OverviewDiscussionsAdmin

Find event

find_event
Read-only

Search for, look up, or locate events and Inbox items by name when you do not have an id: case- and accent-insensitive. Events match fuzzily; Inbox items (un-timed blocks, not events) match when the name holds the query, and come back as inbox (top of tray first, the same shape as the get_schedule backlog items; write them with manage_inbox). Each page has up to 50 Inbox matches; inboxMatchedCount is the total. When nextInboxOffset is not null, pass it as inboxOffset with the same query and filters to read the next page. The offset only pages Inbox items. The date and timeOfDay filters apply to events only. Date ranges include events overlapping any requested day, including events that start earlier; ending exactly at the first midnight does not overlap. timeOfDay filters the event's start time. Events are searched from the past week through the next 30 days by default; pass from/to (ISO "YYYY-MM-DD", e.g. "2026-06-01") to widen or shift the window, and optionally filter by areaId, activityTypeId, or timeOfDay. Returns events (best match first, one per event, each with its name match score from 0 to 1, 1 = exact; a recurring event gives one occurrence with its seriesId: the best match, and on a tie the one nearest to today) in the same event shape as get_schedule, and the timezone of their times. An event with readOnly: true lives on a calendar the user does not own: do not edit or delete it. When two different events tie, ambiguous is true: ask the user which one they meant. Two days of the same recurring event are not ambiguous.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoRange end, ISO date, e.g. "2026-07-01". Defaults to +30 days.
fromNoRange start, ISO date, e.g. "2026-06-01". Defaults to 7 days ago.
queryYesText to match against event names, e.g. "standup", "gym".
areaIdNoOnly match events linked to this area id.
timeOfDayNoOnly match events that start in this part of the day.
inboxOffsetNoInbox page offset from nextInboxOffset; keep the same query and filters. Defaults to 0. Does not page the events.
activityTypeIdNoOnly match events linked to this activity-type id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / llm_model
      Removed value: -{
-  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "query",
-  "llm_model"
-]New value: +[
+  "query"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / inboxOffset
      Added value: +{
+  "description": "Inbox page offset from nextInboxOffset; keep the same query and filters. Defaults to 0. Does not page the events.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  3. Changed1 schema field changed
    • removedInput schema / properties / conversation_id
      Removed value: -{
-  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
-  "type": "string"
-}
  4. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / conversation_id
      Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}
    • addedInput schema / properties / llm_model
      Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "llm_model"
+]
  5. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / timeOfDay / description
      Previous value: -"Only match events starting in this part of the day."New value: +"Only match events that start in this part of the day."
  6. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  7. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint. The description adds substantial behavioral context beyond them: fuzzy event matching, case/accent-insensitivity, Inbox result shape, pagination rules, event-only filter behavior, date-overlap semantics, default time window, scoring, seriesId tie-breaking, and readOnly calendar handling.

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

Conciseness4/5

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

The description is long but front-loads the core purpose and is mostly dense with necessary edge cases for a 7-parameter search tool. It could be tightened slightly, such as the 'Search for, look up, or locate' synonym stack, but the length is largely justified.

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 fully explains the return shape: events, timezone, score, seriesId, inbox results, inboxMatchedCount, nextInboxOffset, and ambiguity handling. It covers the tool's complexity and edge cases thoroughly enough for an agent to invoke and interpret it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema, including that from/to widen or shift the event search window, timeOfDay filters event start time, and inboxOffset pages only Inbox items. It is less detailed for areaId and activityTypeId, which the schema already explains adequately.

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?

States specific verbs and resources: search for, look up, or locate events and Inbox items by name when no id is available. It clearly distinguishes Inbox items from events and ties the event shape to get_schedule, letting an agent separate it from siblings without opening schemas.

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

Usage Guidelines5/5

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

Explicitly says to use this tool when you do not have an id, describes pagination behavior for Inbox matches, and routes writing to manage_inbox. It also explains default search window, how to widen it, and when to ask the user due to ambiguity.

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

All reassign 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