Plugin tracker

Tools

Explore what tracked Claude Connectors and ChatGPT Plugins can actually do. Search by tool, Plugin, Brand, category, verb, or access requirement.

Latest snapshot2026-09-11USmethodology registry-public-v1

Searchable tools

113,017

Authless tools

7,424

Auth required

100,766

Described tools

61,166

113,017 tools

list_forecastslist · List the most recent Mantic forecasts across all questions, newest first, in pages of 25. Pass the returned `next` cursor as `after` to page further back in time. Each item links to its question; use view_question for the full question context or get_forecast for one forecast's details. Prefer search_questions when you are looking for a specific topic rather than browsing the latest activity.ManticManticPluginrequiredData & Analytics
search_dashboard_questionssearch · Search the questions on one dashboard by free-text `search`, or list them (most recently added first, in pages of 25) when no `search` is given. Get the `dashboard_id` from list_dashboards. Pass the returned `next` cursor as `after` to page further (browsing only; search results are not paged). Each item links to its question; use view_question with a returned ID for the full forecast. This is search_questions scoped to a single dashboard.ManticManticPluginrequiredData & Analytics
별자리 운세박사 별자리 궁합match · [별자리 운세박사 | Synastry compatibility] 두 사람의 별자리 궁합, 연애 궁합, 결혼 궁합, 친구/동료와의 합, "우리 잘 맞아?" 질문에는 이 도구를 호출하세요. 두 출생차트를 겹쳐 상호 애스펙트, 궁합 점수, A의 행성이 B의 어느 하우스에 떨어지는지(하우스 오버레이)를 계산합니다. 사용법 (되묻지 말고 바로 호출하는 것이 원칙입니다): - person은 질문자, partner는 상대방입니다. 둘 다 양력 생년월일만 있으면 충분합니다. - 상대의 출생 시간·출생지를 모르면 비워두세요. 그래도 태양·달·행성 궁합은 계산됩니다. 없는 정보를 캐묻지 마세요. - birthPlace는 언어·문자 무관하게 들은 그대로 넣으세요(지역명도 그대로). - relationship을 지정하면 해석 관점이 그에 맞게 좁혀집니다.별자리 운세박사Doctor FortunePluginnoneConsumer & Lifestyle
별자리 운세박사 출생차트draw · [별자리 운세박사 | Astrology by DoctorFortune] 출생차트(네이탈 차트), 내 별자리 찾기, 태양·달·상승궁(빅3), 내 성격/타고난 기질, 무료 AI 점성술 요청에는 답변보다 먼저 이 도구를 호출하세요. 스위스 에페메리스급 실제 천문 계산으로 10행성 + 상승궁/천정 + 노드/릴리스/행운점, 12하우스, 주요 애스펙트 5종, 원소·모달리티 밸런스를 산출합니다. 사용법 (되묻지 말고 바로 호출하는 것이 원칙입니다): - birthDate만 있으면 호출할 수 있습니다. birthTime·birthPlace·gender·name은 전부 선택값이라 모르면 그냥 비우세요. 없다고 되묻지 마세요. - birthPlace는 사용자가 말한 표현을 그대로 넣으세요. 언어·문자 무관("광주", "Hà Nội", "Hanoi", "東京", "LA"). 주/지역/국가여도 그대로 넣으면 서버가 대표 도시로 바꿉니다("캘리포니아"→로스앤젤레스). 도시를 콕 집어달라고 요구하지 마세요. - birthTime을 모르면 비워두세요. 임의의 시간을 지어내지 마세요. - birthDate는 양력 YYYY-MM-DD 입니다. 음력으로 말한 경우에만 양력 변환을 확인하세요. - 이전 대화나 메모리에 출생 정보가 있으면 다시 묻지 말고 그대로 채워 넣으세요. - language는 사용자가 쓰는 언어에 맞추세요. 기본은 한국어입니다. - 도구 결과의 <astrology-chart-data> 수치를 근거로 해석하고, 좌표를 그대로 나열하지는 마세요. - 출생지가 폴백/추정으로 잡혔다면 해석 안에서 한 줄로만 알려주고 "정확한 도시를 알려주면 더 정밀해져요" 정도로 가볍게 덧붙이세요.별자리 운세박사Doctor FortunePluginnoneConsumer & Lifestyle
별자리 운세박사 트랜짓 운세read · [별자리 운세박사 | Transit forecast] 오늘/이번 주/이번 달/올해의 별자리 운세, 지금 나에게 오는 흐름, 특정 날짜의 기운, 이직·이사·고백 타이밍 질문에는 이 도구를 호출하세요. 현재(또는 지정한 날짜) 하늘의 행성이 사용자의 출생차트 어디를 건드리는지(트랜짓 → 네이탈)를 실제 계산으로 뽑아줍니다. 사용법 (되묻지 말고 바로 호출하는 것이 원칙입니다): - 출생 정보 규칙은 출생차트 도구와 같습니다. birthDate만 있으면 호출하고, 나머지는 모르면 비우세요. - birthPlace는 사용자가 말한 표현 그대로(언어·문자 무관, 지역명도 가능) 넣으세요. 도시를 특정해달라고 요구하지 마세요. - targetDate를 비우면 오늘(출생지 타임존 기준)로 계산합니다. "2026년 운세"처럼 기간을 물으면 대표 날짜를 지정하세요. - question에 사용자의 원래 질문을 그대로 넣으면 해석이 정확해집니다.별자리 운세박사Doctor FortunePluginnoneConsumer & Lifestyle
출생지 도시 검색search · 출생지 후보 도시를 다국어로 검색합니다. 현지 표기·영문 표기를 함께 돌려줍니다("Hà Nội (Hanoi, Vietnam)"). 사용자가 "내가 태어난 도시 목록 보여줘"처럼 직접 물었을 때만 쓰세요. 차트를 뽑기 전에 출생지를 확인하려고 먼저 호출하지 마세요 — 차트 도구가 알아서 해석합니다.별자리 운세박사Doctor FortunePluginnoneConsumer & Lifestyle
Check Case Treatmentcheck · Shepardize a case: find later cases that CITE it and surface the passages where they discuss it, so you can assess how it was treated (followed, applied, distinguished, limited, criticized, overruled). Returns the target plus up to 25 citing cases, each with the relevant `highlights` and the citing case's `citation_count` (its authority). Pass the case `id` from a search/lookup result (CASES only). Each citing case carries `treatment_flag`: "negative" (overruled/abrogated), "cautionary" (distinguished/criticized/limited), or null (neutral). Cases are ranked treatment-first, then by court hierarchy — a case can only be overruled by an equal-or-higher court, so a negative treatment from such a court (the likeliest real overruling) is surfaced ABOVE the lower courts that merely discuss it, then by recency. LEAD your answer with any negatives from a peer/higher court. Still READ the highlights to confirm — the flag is a heuristic signal, not a verdict (lexical, negation-aware, and target-associated: the verb must appear near the target's citation or party name, but there is no true citation graph behind it). IMPORTANT — two different counts: `total_citing_cases` is how many are RETURNED in this response (≤25, what you actually analyzed); `total_citing_cases_found` is the TRUE total number of citing cases matched before that cap. When telling the user how many citing cases exist or were searched/checked, always use `total_citing_cases_found` — saying 'we checked total_citing_cases cases' understates the real search whenever `treatment_completeness` is "partial" (total_citing_cases_found > total_citing_cases). When `treatment_completeness` is "partial", tell the user the analysis is a ranked subset and to confirm against a full citator. NOT a citation-format check (use verify_citations for that).CiteLawCiteLawPluginrequiredOperations
Check Corpus Coveragecheck · Report exactly how much material CiteLaw holds for a jurisdiction and/or authority type — e.g. "do you have Tennessee statutes?". Reads a nightly census of the corpus, so it is instant and free, and does not count against research quotas. ALWAYS call this before telling a user that CiteLaw does or does not cover something. A search returning no results is NOT evidence of no coverage — only this tool is. Both arguments are optional: `jurisdiction` alone returns every authority type held for that state; `source` alone lists every jurisdiction covered for that authority type; both together give a direct answer; neither gives a corpus-wide summary. Accepts "TN" or "Tennessee". Each answer carries a `status`: `covered` (we hold it, with a count), `not_covered` (we genuinely hold zero — say so plainly), `not_tracked` (we may hold it but do not count that dimension — report as unknown, NEVER as "no"), `not_applicable` (the dimension is meaningless, e.g. immigration agency material is national), or `unavailable` (no census on this deployment — coverage unknown).CiteLawCiteLawPluginrequiredOperations
Create Contactcreate · Add a new person or organization to the firm's shared address book (the user's workspace). Returns the created contact's `contact_id` and merge fields. ONLY call this when the user EXPLICITLY asks to add/save a contact ("add Jane Smith to my contacts", "save them as opposing counsel") — or, during workflow intake, when the user names a recipient/party who isn't on file yet AND gives you their details. NEVER call it proactively or to be helpful. Before creating, prefer query_contacts to check the person isn't already on file. After creating, confirm briefly — the user sees an editable card to correct any details.CiteLawCiteLawPluginrequiredOperations
Create Documentcreate · Save the document you DRAFTED earlier in this chat as a Word (.docx) in the user's CiteLaw matter (it becomes a native document — readable and editable like an upload). AFTERWARDS it can be read with read_document and found by search_documents in mode "keyword". It is NOT indexed for semantic search — search_documents in mode "semantic" will not find it until someone indexes it in the CiteLaw app, which is a separate opt-in because embedding costs money. So if the user asks you to search a document you just saved, use keyword mode. HOW IT WORKS: first draft the document in a chat message wrapped in a ```document fence (per the drafting rules) — conversational text stays OUTSIDE the fence. Then, when the user asks to save it, call this with just a `file_name`; it converts the body of your most recent ```document fence into the .docx (chatter outside the fence is excluded), or pass the body directly as `markdown` (e.g. over MCP). If there is no drafted document yet, draft it first. FORMAT: Word .docx only. If the user wants a PDF or other format, tell them CiteLaw saves Word documents and they can export from there. ONLY call this when the user explicitly asks to save/create the document. After saving, confirm briefly with the document name.CiteLawCiteLawPluginrequiredOperations
Create Notecreate · Save a note to the user's CiteLaw workspace, optionally linked to authorities from this session's tool results. ONLY call this when the user EXPLICITLY asks you to create, save, or take a note ("save a note about this", "note that down", "create a note linking these cases"). NEVER call it proactively — not to be helpful, not to summarize your own answer, not because something seems noteworthy. No explicit instruction, no note. Link the authorities the note discusses via the `authorities` array using ids from THIS session's search/lookup results. After saving, confirm briefly — don't repeat the full note content back.CiteLawCiteLawPluginrequiredOperations
Extract Citationsextract · Pull citations out of text using eyecite. ALWAYS run this first when the user provides a document, brief, or pasted passage and wants its citations checked — then pass the results to `verify_citations`. TWO input modes: for an UPLOADED/stored document pass `document_id` (the server reads the full text itself — NEVER re-type or summarize document text into `text`; a partial or placeholder value extracts nothing); for text the user pasted into chat, pass `text`. When you do, pass each citation as a STRUCTURED OBJECT, not just the raw string: build { citation, title, year, court } from the extracted row — citation from the clean cite (no pin cites; use canonical volume/reporter/page), title as "{plaintiff} v. {defendant}" from metadata, plus year/court when present. The extra fields are what let verify_citations confirm the cite actually refers to the claimed case instead of merely existing. Returns structured citation rows: each has the raw text span, type (full / short / id / supra / unknown / docket), char span, canonical { volume, reporter, page } for case citations, and metadata { plaintiff, defendant, year, court, pin_cite, parenthetical }. Short/id/supra citations refer back to an earlier full citation — verify the FULL citations and skip the reference forms. DOCKET-ONLY cites are also extracted (type='docket'): cases cited by docket number with no reporter cite (recent slip opinions, motions, appeals). Each docket row carries `docket_number` and, when found nearby, `case_name` — pass these to verify_citations as { docket_number, title } (the docket is the primary lookup key when there's no reporter cite). eyecite is CASE-citation-first: statute citations come back type='unknown' with minimal metadata; if you already know the statute strings, skip extract and call verify_citations directly with them.CiteLawCiteLawPluginrequiredOperations
Fetch Authorityfetch · Fetch the full text and metadata of a CiteLaw authority by id. Use ids returned by the search tool, e.g. "cases:<id>".CiteLawCiteLawPluginrequiredOperations
Get Active Workspace/Matterget · Show which CiteLaw workspace and matter this session is currently working in. Call this when the user asks where their work is being saved, or before saving a note if you're unsure of the active matter.CiteLawCiteLawPluginrequiredOperations
Get Workflow Instructionsget · Fetch one saved CiteLaw workflow's full run instructions (find its id with list_workflows). The result's `instructions` are the user's own standardized process — follow them faithfully in this conversation: gather the listed inputs, do the research with the CiteLaw tools, produce EXACTLY the output structure described (fixed text verbatim), and save document deliverables with create_document. Note: extraction-table workflows run best inside the CiteLaw app, where per-row authority research fills automatically. Read-only.CiteLawCiteLawPluginrequiredOperations
Keyword Search Case Lawsearch · Westlaw-style Boolean keyword search across CiteLaw's legal authority corpora (cases, statutes, court rules). NOT the default search tool — use this ONLY when the user wants EXACT-phrase or BOOLEAN term-matching. For conceptual / semantic questions ("What's the law on X?", "Find cases about Y"), use `search_authorities` instead — its hybrid ranking surfaces relevant authorities even when exact words don't match. Pick this tool when the user: • puts terms in quotes ("reasonable doubt") • combines terms with AND / OR / NOT • asks whether any authority CONTAINS a specific phrase • asks for proximity matches (/3, /S, /P) or wildcards (*, %) ALSO USE FOR QUOTE VERIFICATION. Before quoting any case or statute text in your answer, run this tool with the exact phrase in quotes — the returned highlights show the matched wording in surrounding context, which is BOTH proof the quote is real AND its source attribution in one call. Quote ONLY the text that comes back; never reconstruct quoted text from training memory. CONTENT-ONLY — searches case abstracts and statute / court-rule section text, never metadata. To find an authority by citation, case name, code, or section, use `authority_search_metadata`. Also searches local_rules, judge_practices, agency_decisions, agency_guidance, and regulations. Returns up to `limit_per_source` results per source (default 10), each with up to `snippets_per_item` highlighted passages (default 10) — match terms wrapped in **bold** so you can see exactly what hit. Statute search always includes federal U.S. Code; jurisdiction is optional there (add state abbrevs to also search their codes).CiteLawCiteLawPluginrequiredOperations
Link Contact To Matterlink · Associate an existing contact with the user's CURRENT matter, optionally recording the role the contact plays on that matter. Returns the link's contact, matter, and role. ONLY call this when the user EXPLICITLY asks to add/associate/link a contact with the matter ("add Jane to this matter", "she's the client on this case"). NEVER call it proactively. The contact must already exist — search with query_contacts (or create it with create_contact) first, confirm the right match, then link it. The matter is always the session's current matter; you cannot link into a different one.CiteLawCiteLawPluginrequiredOperations
List Documentslist · Find / list the documents in the user's active CiteLaw matter by METADATA (everything they've uploaded, created, or pulled in from connected storage). Returns references (id, name, source, type, date, indexed) — NOT content; use read_document to read one or search_documents to search inside their text. This is the metadata lookup: filter by name (`q`), file type, provenance, how it arrived, indexed status, and a created-date range, and sort. `indexed:true` means a doc is available to semantic search. All filters combine (AND). Scope is the session's active matter.CiteLawCiteLawPluginrequiredOperations
List Matterslist · List the matters (matters) in the active workspace. Use a returned `id` with switch_matter to change the working matter.CiteLawCiteLawPluginrequiredOperations
List Saved Workflowslist · List the user's saved CiteLaw workflows — their standardized, reusable processes (client letters, memo formats, contract review checklists, status updates). Covers CiteLaw's built-in workflows plus everything saved in the user's workspace, including colleagues' workflows. Use this when the user asks to run, follow, or use one of their workflows/templates, or asks what workflows they have. Then call get_workflow with the chosen id and follow its instructions in this conversation. Read-only.CiteLawCiteLawPluginrequiredOperations
List Workspaceslist · List the workspaces the user belongs to (with the active one flagged). Use the returned `id` with switch_workspace to change the working workspace.CiteLawCiteLawPluginrequiredOperations
Look Up Judgejudge · Look up a FEDERAL JUDGE by name and get their complete profile: role, court, biography (appointing president, judicial service history, education, birth year), federal caseload statistics (assigned cases and referred matters from the docket archive), and — most importantly — their chambers STANDING ORDERS and INDIVIDUAL PRACTICES with full text. Covers ~1,200 federal district, magistrate, and bankruptcy judges whose chambers practices CiteLaw has collected. USE THIS WHEN the user asks about a judge: "what are Judge Anderson's summary judgment requirements?", "who is Magistrate Judge Pym?", "how do I schedule a conference before Judge X?", "tell me about the judge on my case". This is the ONLY tool with judge biographies and caseload stats; practice text is also reachable per-document via authority_lookup (source='judge_practices'). NOT for finding opinions a judge wrote (use search_authorities) and NOT for state court judges (federal only). Resolution: pass the name as given — honorifics and partial names are fine. If several judges match you'll get `multiple_matches` with slugs; re-call with the slug as judge_name. A `court` hint (any fragment: "SDNY", "C.D. Cal", "bankruptcy") disambiguates common surnames in one call. Citing: each practice document carries a `citelaw_cite` markdown link — use it verbatim when referencing the judge's orders, per the standard citing rules. Practice text is budgeted (~20K chars per call); `truncated: true` + the guidance field tell you when to follow up with authority_lookup for a specific document.CiteLawCiteLawPluginrequiredOperations
Manage Clausesmanage · Add to and maintain the firm's clause library: save a provision for reuse, correct one, archive language the firm has stopped using, or remove one saved by mistake. Use when the user asks you to remember a provision, or after drafting language they say they want to keep. Built-in clauses cannot be changed; create a new one from their text instead.CiteLawCiteLawPluginrequiredOperations
Manage Contactsmanage · Add or update MANY contacts at once — importing a client list, the parties from a pleading, or a set of opposing counsel. Use this instead of create_contact whenever there is more than one. Contacts already in the address book are matched and left alone rather than duplicated, so re-running an import is safe. The result reports created versus already-existed for every row: tell the user both numbers. Pass external_provider and external_id when importing from another system so a future sync updates the same records. For thousands of rows, the CSV import in the CiteLaw app is the better tool.CiteLawCiteLawPluginrequiredOperations
Manage Discoverymanage · Create, change and remove discovery sets and the numbered requests inside them. Use when the user pastes or shares discovery they were served, asks you to draft responses and objections, or wants to correct or remove something. Pair with read_document to load a served PDF: read it, work out where each request begins, then add them here. Always belongs to the current matter.CiteLawCiteLawPluginrequiredOperations
Manage Leadsmanage · Create, update, or convert prospective clients in the intake pipeline. Use create/update when the user describes someone who has enquired. Use convert when the user explicitly asks to open a matter for, sign, or convert a lead: it creates the matter from the lead's intake fields, promotes the lead to a client contact, and marks the lead converted, so prefer it over manage_matters create in that situation. Never convert unprompted.CiteLawCiteLawPluginrequiredOperations
Manage Mattersmanage · Create and maintain matters: open a new one, rename it, describe it, archive one that is finished (or restore it), and control which workspace members can see it. Use when the user asks to set up a matter for a new client or piece of work, tidy up their matter list, or give a colleague access. A new matter does NOT become active on its own; follow create with switch_matter if the user wants to start working in it. Ids must come from list_matters. Archiving is reversible and hides nothing permanently; matters cannot be permanently deleted here.CiteLawCiteLawPluginrequiredOperations
Manage Schedulemanage · Create, update, or delete the user's schedule items: matter DEADLINES (the litigation timeline) or CALENDAR EVENTS (their CiteLaw calendar — changes mirror to the user's Outlook automatically when it's connected). One action + one item_type per call; `items` takes many at once, so a whole scheduling order is ONE call. ONLY call this when the user explicitly asks to add, change, complete, or remove schedule items, or confirms dates you proposed (e.g. after you read a scheduling order). Never write proactively. For update/delete, `id` must come from a query_schedule result THIS session — query first, never invent or recall ids. Dates are ISO 8601; give calendar events concrete UTC start/end times unless all_day.CiteLawCiteLawPluginrequiredOperations
Manage Tasksmanage · Create, update, or complete tasks (assignable work) in the current matter or at the firm level. Use when the user asks you to note something that needs doing, assign work, or mark work finished. Cannot approve or reject items in the review queue — those are decided by a person in the app.CiteLawCiteLawPluginrequiredOperations
Manage Workflowsmanage · Create, update, or delete the user's own CiteLaw workflows — their saved, standardized processes. Use it to turn an existing template the user pastes or describes (a client letter, a memo format, a review checklist) into a reusable workflow, or to refine one they created. `workflow` takes: name (required on create), description, mode ("ask" research | "draft" document | "review" analyze-a-document), inputs (fields the user fills per run: name, label, type [text|textarea|document|number|currency|select|radio|multi_select|date|jurisdiction|authority_reference|contact_reference], required, help, options), system_addendum (extra standing instructions; may reference inputs as {{input_name}}), and output — {shape: "document"|"conversational", sections: [{label, key, content_type [paragraph|multi_paragraph|bullet_list|numbered_list|verbatim_quote|summary_sentence|verbatim_text], description, required, verbatim_text}], header, footer} or {shape: "extraction_table", columns: [...]}. Put fixed boilerplate (signature blocks, notices) in verbatim_text sections so it reproduces exactly. Updates may pass just the fields to change. Only the user's own workflows can be changed — never CiteLaw's built-ins, never a colleague's. Confirm with the user before deleting.CiteLawCiteLawPluginrequiredOperations
Manage Workspacemanage · Set up and run the firm behind a workspace: create a new team workspace, rename one, invite colleagues, set what each member is permitted to do (workspace role) and what they do at the firm (firm role), set billing rates, and remove people who have left. Every action except create requires workspace owner or admin permission. Inviting emails a real person and consumes a firm seat immediately; removing someone ends their access and their entitlement. Use query_firm first to see who is there, what they hold, and how many seats are free. Accepting invites, leaving, and billing changes are done by the person themselves in CiteLaw.CiteLawCiteLawPluginrequiredOperations
Query Clausesquery · Search the firm's clause library — its own standard contract and letter language, plus a built-in starter set. Use BEFORE drafting a provision the firm likely has standard wording for (confidentiality, indemnity, governing law, arbitration).CiteLawCiteLawPluginrequiredOperations
Query Contactsquery · Search the firm's shared address book for a person or organization — a client, opposing party, opposing counsel, court, witness, or vendor. Returns each match's `contact_id`, name, type, organization, and email, plus `merge_fields`: everything the firm has on file for addressing this contact in a document (salutation, formal_name, phone, address lines, and a ready-to-print multi-line address_block). When drafting a letter or document to a contact, use merge_fields values verbatim. A field absent from merge_fields is NOT on file — ask the user for it, never invent it. By default (scope "matter") this searches only the contacts associated with the CURRENT matter, and each result includes a `matter_role` (the contact's role on this matter). Pass scope "workspace" to search the firm's entire address book instead — use that when the person may not be linked to this matter yet. Search also matches a contact's PRIOR names and organizations, so a client now named "Miller" still surfaces when searched as "Johnson". When a result matched on an old value it carries `former_names` / `former_organizations` — surface that to the user (e.g. "Jane Miller, formerly Johnson") so the match is clear. Use this whenever the user refers to someone who might be on file ("my client Jane Smith", "opposing counsel at Acme") or when a workflow needs a contact_reference — search first, then confirm the right match with the user before relying on it. Never invent a contact_id; only use ids returned here. NOT the same as query_leads. A CONTACT is someone on file for work the firm has already taken on. A LEAD is a prospective client who has not been signed and has no matter yet. If you cannot tell which the user means, search BOTH before saying the person is not on file.CiteLawCiteLawPluginrequiredOperations
Query Discoveryquery · List discovery served on or by the firm for the current matter, or open one set to read its numbered requests and responses. Use for 'what discovery is outstanding', 'what's due', or before drafting responses.CiteLawCiteLawPluginrequiredOperations
Query Firmquery · Look up the firm behind the active workspace: who its members are, what workspace role and firm role each one holds, how many seats the firm plan provides and how many are in use, which invitations are still outstanding, and (for owners and admins) recent workspace activity. Read-only. Use it before inviting someone (to check seats), before changing anyone's permissions (to see what they hold today), or when the user asks who is on their team. To CHANGE any of it, use manage_workspace. This is about the workspace you are in; list_workspaces is about which workspaces you belong to.CiteLawCiteLawPluginrequiredOperations
Query Leadsquery · List prospective clients in the firm's intake pipeline. Use for 'what leads are open', 'has anyone followed up with X', or to find a lead before running a conflict check. NOT the same as query_contacts. A LEAD is a prospective client the firm has not taken on: no matter exists yet, and converting the lead is what creates one. Someone the firm already acts for or against — client, opposing party, opposing counsel, witness, court, vendor — is a CONTACT; use query_contacts for those. A lead that has already converted usually exists in both places. If you cannot tell which the user means, search BOTH before saying the person is not on file.CiteLawCiteLawPluginrequiredOperations
Query Notesquery · Search/list the user's saved notes in the active CiteLaw workspace/matter. Returns note text + any linked authorities. The scope (workspace/matter) is the session's active matter — you control only `q` (search text), `sort`, and paging.CiteLawCiteLawPluginrequiredOperations
Query Schedulequery · Read the user's schedule: matter DEADLINES (the litigation timeline of the active workspace/matter) and CALENDAR EVENTS (their CiteLaw calendar, including Outlook-synced events), merged chronologically over a date window. Default window: today through +90 days; pass start/end for a different range (past ranges are fine). Every item carries its `id` and `item_type` — exactly what manage_schedule needs to update or delete it. Call this BEFORE any update/delete so you act on real ids, never remembered or invented ones. Re-run it whenever you summarize or report the schedule, even if earlier results are visible in this conversation — the schedule may have changed since (other sessions, the calendar tab, Outlook sync); this call is the live source of truth. When events carry `start_local`/`end_local`, quote THOSE times to the user, never convert UTC timestamps yourself.CiteLawCiteLawPluginrequiredOperations
Query Search Historyquery · Look through the user's past CiteLaw chats in the active matter — the research they did in the CiteLaw app itself. Read-only. Call with no arguments (or `q` to search titles) to LIST the matter's chats. Then pass `session_id` from that list to READ one in full: every question asked and every answer given. Use it before repeating work — to pick up where the user left off, or when they refer to something they 'already looked into' in this matter.CiteLawCiteLawPluginrequiredOperations
Query Tasksquery · List tasks (assignable work) in the current workspace. Use for 'what's on my plate', 'what's outstanding on this matter', or to find items waiting for approval. Covers both matter work and firm-wide admin work. Read-only.CiteLawCiteLawPluginrequiredOperations
Read Documentread · Read the full text of one of the user's documents, by id, paged by character. Pass `id` for a document from list_documents (an uploaded or connected-storage file). Returns a window of text from start_char; page long documents via has_more / next_start_char. Use this when you need a document's actual wording; use search_documents to find content across documents.CiteLawCiteLawPluginrequiredOperations
Search Authorities by Metadataauthority · Look up authorities by BIBLIOGRAPHIC METADATA (title, citation, code, section, docket, court) — NOT by content. Use this when the user describes WHICH authority they want by how it's catalogued, not by what it discusses. THIS IS THE TOOL FOR FINDING A SPECIFIC, ALREADY-NAMED AUTHORITY. Always prefer it over `search_authorities` for known-item lookups (a case name, a citation, a code + section): it matches the catalogued title/citation/section directly, while semantic search ranks by topic and can bury or miss the exact case the user named. Pick this tool when the user: • names a case ("Roe v Wade", "Smith v Jones") • pastes a citation ("410 U.S. 113", "123 F.3d 456", "CPLR § 3013") • cites a statute by code + section ("NY UCC 2-201", "22 NYCRR 205.23") • gives a docket number ("21-1234") Do NOT use this for content questions — for "What's the law on X?" use `search_authorities`. For "Find passages that mention exact phrase X" use `search_authorities_keyword`. To read the full text of a result, use `authority_lookup` with the `id` returned here. Do NOT use this to VERIFY or CHECK a LIST of citations — a Table of Authorities, a brief's cites, "are these citations real?" — that is `verify_citations`' job, in ONE bulk call (up to 50 at once). Per-item metadata lookups are the wrong tool for verification: they burn a round per citation and a bare title search returns loose near-matches (same party name in another state, a different era) with no confirmed / possible_match / no_match verdict. This tool is for finding ONE authority the user wants to use, not for auditing many. `source` is REQUIRED — pick the one that matches the kind of citation/metadata you have (a case citation only finds cases, etc.). For cases: provide at least one of `title`, `citation`, `docket_number`. For statutes: REQUIRES `jurisdiction` (state abbrev, or "US" for the U.S. Code) plus at least one of `code_name`, `section_number`, `section_name` — or just pass the whole `citation` ("42 U.S.C. § 9601") and it will be split for you. For court_rules: at least one of `code_abbrev`, `section_number`. Returns ranked candidates — top result is usually the right one but always inspect.CiteLawCiteLawPluginrequiredOperations
Search CiteLawsearch · Search CiteLaw's US legal corpus with a free-text query. Searches case law, statutes, and court rules by default; pass `sources` to reach court-specific local rules, individual judges' standing orders, immigration agency decisions and guidance, or administrative regulations. Returns matching authorities with ids for use with the fetch tool and citelaw.org URLs for citation.CiteLawCiteLawPluginrequiredOperations
Search Document Templatesquery · Search the firm's document templates — their OWN uploaded .docx letterhead, pleading, and letter shells with {{token}} placeholders that merge into perfect-fidelity Word documents. Use when the user names a firm document to generate ('our engagement letter', 'the standard fee agreement'). This is a single fill, not a process: for multi-step firm procedures use list_workflows instead, and for reusable paragraphs of language use query_clauses.CiteLawCiteLawPluginrequiredOperations
Search Documentssearch · Search the user's OWN documents (the files attached to their CiteLaw matters — uploads and documents pulled in from connected storage). Two modes: - mode:"semantic" (default) — meaning-based passage search; covers ONLY documents the user has indexed for AI search. Best for "what does my contract say about termination". - mode:"keyword" — exact term/phrase search over EVERY document's extracted text (no indexing needed). Best for "where does my contract say 'indemnify'". Pass `document_id` to scan one document. For published law use search_authorities; to read one document in full use read_document. Scope is the workspace; set `scope`:"matter" to limit to the active matter.CiteLawCiteLawPluginrequiredOperations
Switch Matterswitch · Change the active matter (matter) within the current workspace. Pass a `matter_id` from list_matters — NOT an id you guessed. Notes and saved work after this attribute to the new matter. Only switch when the user asks to work in a different matter.CiteLawCiteLawPluginrequiredOperations
Switch Workspaceswitch · Change the active workspace to one the user belongs to. Pass a `workspace_id` from list_workspaces — NOT an id you guessed. Starts a fresh session scoped to that workspace's default matter. Only switch when the user asks to work in a different workspace.CiteLawCiteLawPluginrequiredOperations
Verify Citationsverify · Verify that citations refer to authorities present in the CiteLaw corpus — and catch typos. Covers case law, statutes, court rules, administrative regulations (C.F.R. / state admin codes), and immigration agency decisions (BIA / AAO, "I&N Dec.") — auto-detected per citation, so just pass them all. ONE call does everything: pass EVERY citation at once. If the user gave a DOCUMENT, run `extract_citations` with its `document_id` first, then pass each citation here as an object { citation, title, year, court, docket_number } (title from plaintiff/defendant). If the user PASTED citations directly into chat (a Table of Authorities, a citation list), pass them straight here — `extract_citations` is NOT required for pasted lists, and NEVER verify a list via per-item `authority_search_metadata` lookups (slower, costlier, and bare title searches return unranked near-misses, not verification verdicts). Docket-only citations are valid — pass docket_number with no citation. Each citation is classified: "confirmed" (we have this exact authority), "possible_match" (a near-miss — the cite resolves to a slightly different case, or a strong title match exists under a different cite; almost always a TYPO, returned with ranked `candidates` and per-field `field_matches` so you can say "did you mean…?"), or "no_match" (not in our database — which is NOT the same as the citation being fake or invalid). This tool is COMPLETE on its own. Never re-call it with fewer fields, and never follow it with search_authorities / authority_search_metadata to hunt for no_match citations — report them as not-in-database and stop. After one call, summarize the results for the user. NOT a treatment-status check (overruled, criticized) — that's a separate tool. Max 50 citations per call; run in parallel.CiteLawCiteLawPluginrequiredOperations
2D cross-tab of two dimensionsatlas · Cross-tabulates two fields (x by y) with per-cell counts and an optional metric — heatmap/matrix data (e.g. propertyType by city). EITHER AXIS MAY BE A DATE FIELD (createdAt, transactionDate, date): it is then bucketed as a calendar period via `interval`, which is how you get a per-group TIME SERIES — e.g. xField=propertyType + yField=transactionDate + interval=quarter returns quarterly counts per property type in ONE call instead of one query per period. Charges a fixed credit cost (meta.creditCost).RED Atlas APIRED AtlasPluginrequiredData & Analytics
Aggregated market statsatlas · Aggregated statistics for a (market, entity) pair — counts, price/area aggregates, percentiles, distributions and derived metrics (e.g. `derived.pricePerBuiltAreaMedian`). Optionally add an ad-hoc `groupBy` breakdown, custom `percentiles`, or an outlier-robust `trimmed` mean. On listings and transactions the response also carries `excludingOutliers` — the same price aggregates computed without the documents ingest flagged as `isOutlier` (scraped placeholder prices such as a $99,900,000 "call for price" listing). QUOTE `excludingOutliers` FOR ANY MONEY TOTAL OR AVERAGE; the top-level `priceStats` is the unfiltered figure and can be inflated by a handful of placeholders. Charges a fixed credit cost (reported in meta.creditCost). Supports the same filters as atlas_query_data.RED Atlas APIRED AtlasPluginrequiredData & Analytics

Tool Explorer FAQ

What is Tool Explorer?

Tool Explorer indexes the callable tool names and descriptions attached to public registry profiles. It is useful for seeing what agents can actually invoke, not just which profile exists.

How do category and verb filters work?

Category filters use the live registry category rollup. Verb filters use the public tool insights rollup, so the page stays backed by the same read models as the tracker charts.

Why do auth requirements matter?

Auth requirements show whether a tool is likely usable without account connection, requires authentication, is private, or is unknown in the current snapshot.