OrgLines

Search personal records

search_personal

Read-only

Unified search across ALL of the caller's workspace data — notes, tasks, remembered facts, calendar events, inbox, documents, goals, reading list, prompts, decisions, wiki, meeting notes, tracked documents (passports/visas/insurance), subscriptions, warranties, people in the personal contact book (type 'contact', fuzzy + transliterated), and CRM leads (when the workspace has the Lead Center). Read-only. Returns ranked matches, each carrying its type, id, title and a snippet. Pass 'types' to restrict to specific entity types (e.g. ['note','lead']); omit it to search everything. Pass 'include_kb': true to ALSO federate top matches from the workspace's Knowledge Base (tagged 'kb_chunk'). Use to answer 'what did I write / note / remember / file about X'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_personal"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`query`	Yes
`types`	No	Optional list of entity types to restrict the search to (e.g. ['note','task','lead']). Omit to search all types.
`include_kb`	No	When true AND the workspace has a Knowledge Base, also return top KB chunk matches (type 'kb_chunk'). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond them: the ranked-match return shape (type, id, title, snippet), the 'kb_chunk' tagging for federated KB results, and the fuzzy/transliterated contact matching. Minor gaps remain around ranking method and pagination behavior.

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?

Scope and read-only status are front-loaded, and the operational guidance for 'types' and 'include_kb' follows. The long entity-type enumeration is dense but earns its place by defining search coverage; a bulleted structure would read slightly better but nothing is truly wasted.

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

Completeness4/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 carries the return-value burden and does so adequately (ranked matches with type, id, title, snippet). For a 4-parameter read tool the remaining unknowns are small: the 'limit' default and how ranking/truncation works.

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 only 50%, so description support matters, and it does explain 'types' (with an example and the omit-to-search-everything default) and 'include_kb' federation semantics. It does not explain 'limit' behavior at all (default value, max 50, effect on truncation), leaving one parameter undocumented in both places.

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?

The description opens with a specific verb and resource ('Unified search across ALL of the caller's workspace data') and then enumerates the covered entity types, so an agent can tell this is the broad, cross-type searcher rather than a type-specific sibling like kb_search or search_leads. It also states the read-only nature and the result shape up front.

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

Usage Guidelines4/5

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

It gives a concrete when-to-use framing ('Use to answer what did I write / note / remember / file about X') and explains how to narrow scope with 'types'. It never says when NOT to use this versus narrower siblings (e.g. kb_search for KB-only, find_contact_personal for contacts), so the exclusions an agent most needs are absent.

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

All OrgLines 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?