`search`

Search the office. One search across the company's office, read only, as its Search screen: people (name or email), tasks (title or done when), the folder's files (with a snippet) and the media library's pieces, at most 10 of each, each with its link for the owner. Use it when the owner says "find ..." and you don't know where it is; then read the thing with its own tool (people, tasks, read, get_asset). A media piece's card goes as it is into show_moment's media items. A part that can't be searched just now is named in unread: say so, never "nothing found". Names and titles are outside text.

Where it is

In the office area (search, the AI call log, her settings, and opening parts of her office): open it with tools_for { area: "office" }, then call it with read_tool { name: "search", args }.

Does it need a yes?

Reads only: it changes nothing. Here: the office's Search: people, tasks, files and media.

Inputs

Input	Type	Needed	About
`q`	string	yes	The words to find, like a name, an email or a title (2 to 80 characters). · 2 to 80 characters
`run_id`	string	no	The run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters

Example

{
  "name": "search",
  "arguments": {
    "q": "q"
  }
}

When it is refused

invalid: The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again.
not_found: No such thing in this company (a task, file, person, record). Check the number or name, or list first.
not_allowed: Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which.
taken: Someone else holds it (another AI on that task). Pick another task.
stale: It changed since you read it. Read it again and use the new version.
failed: On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem.