Back to tracker
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-12USmethodology registry-public-v1
Searchable tools
113,018
Authless tools
7,424
Auth required
100,766
Described tools
61,167
113,018 tools
- Criar link temporário de localizaçãocreate · Cria no Monipró um link público temporário para acompanhar a localização de um veículo ou MoniTag. Antes de invocar a ferramenta, informe claramente o alvo e a validade e obtenha a confirmação explícita do usuário. Validades permitidas: 1, 3, 6, 12 ou 24 horas. A API gera automaticamente uma descrição auditada como criada pelo ChatGPT. Ao concluir, sempre mostre a URL completa retornada. Cada chamada cria um novo registro.MonipróMoniPró
PluginrequiredOperations - Desativar aviso de movimentodisable · Remove somente avisos de movimento pendentes do alvo autorizado identificado por placa, descrição completa ou parcial, ou ID do rastreador. Descrições parciais precisam identificar um único alvo. Avisos já disparados são preservados. Confirme o alvo antes de executar.MonipróMoniPróPluginrequiredOperations
- Diagnosticar rastreadordiagnose · Apresenta diagnóstico determinístico do rastreador associado a um veículo ou MoniTag: comunicação, validade GPS, satélites, tensão, modelo, firmware, intervalo de envio e comandos pendentes. Não invente causa técnica; descreva somente os indicadores e problemas retornados. Não altera dados.MonipróMoniPróPluginrequiredOperations
- Gerar ranking operacional da frotaget · Gera ranking dos veículos e MoniTags por distância, utilização ou tempo parado em um período inclusivo de até 7 dias. rankingType deve ser distance, utilization ou stopped. A utilização é o percentual do tempo observado em movimento sobre movimento mais parada. Não altera dados.MonipróMoniPróPluginrequiredOperations
- Listar alertas do veículo ou taglist · Lista até 50 eventos recentes de um veículo ou MoniTag autorizado, incluindo excesso de velocidade, movimento, segurança, ignição, energia e cercas. O alvo pode ser placa, descrição completa ou parcial, ou ID do rastreador. Sempre informe hours e speedOnly. Não altera dados.MonipróMoniPróPluginrequiredOperations
- Listar avisos de movimento ativoslist · Lista até 100 veículos e MoniTags autorizados que possuem aviso de movimento pendente em aviseme. Não inclui avisos já disparados e não altera dados.MonipróMoniPróPluginrequiredOperations
- Listar paradas do veículo ou taglist · Lista paradas de um veículo ou MoniTag em um período inclusivo de até 30 dias. Informe minimumMinutes entre 5 e 1440; somente paradas com duração igual ou superior serão retornadas. Converta expressões de data para YYYY-MM-DD. Não altera dados.MonipróMoniPróPluginrequiredOperations
- Listar veículos disponíveislist · Lista até 100 veículos e MoniTags que a conta Monipró conectada pode consultar, incluindo placa, descrição, tipo e ID do rastreador. Use quando o usuário não souber qual identificação usar ou quando uma descrição puder corresponder a mais de um alvo. Não altera dados.MonipróMoniPróPluginrequiredOperations
- Listar viagens do veículo ou taglist · Lista as viagens calculadas de um veículo ou MoniTag em um período inclusivo de até 30 dias, com início, fim, duração, distância, velocidade máxima e endereços. Converta hoje, ontem ou esta semana para startDate e endDate no formato YYYY-MM-DD. Não altera dados.MonipróMoniPróPluginrequiredOperations
- Localizar ativos mais próximos de um endereçofind · Localiza os veículos e MoniTags mais próximos de um endereço usando a última posição GPS válida. A distância retornada é em linha reta, não distância rodoviária. O endereço é geocodificado pelo Google; confirme o endereço resolvido na resposta. Não altera dados.MonipróMoniPróPluginrequiredOperations
- Pedir relatório operacional à MarIAget · Obtém os dados consolidados para um resumo ou relatório operacional de um veículo ou MoniTag autorizado em um período inclusivo de até 30 dias. Use esta mesma ferramenta quando o usuário pedir resumo operacional, relatório operacional, análise de trajetos ou uma pergunta sobre a operação do período. O alvo pode ser placa, descrição completa ou parcial, ou ID do rastreador. Converta expressões como hoje, ontem ou últimos dias em startDate e endDate antes da chamada. Depois de receber os dados, responda em português do Brasil como MarIA, analista operacional de frotas do Monipró, e diga explicitamente na abertura que a análise ou resposta foi preparada pela MarIA. Use somente os totais, viagens, paradas e eventos retornados; não refaça cálculos, não invente causas e declare qualquer truncamento indicado em limits.MonipróMoniPróPluginrequiredOperations
- Rankear veículos por excessos de velocidaderank · Rankeia os veículos e MoniTags autorizados pela quantidade de eventos reais de excesso de velocidade em um dia ou período inclusivo de até 30 dias. Converta hoje, ontem ou outro período para YYYY-MM-DD. Não altera dados.MonipróMoniPróPluginrequiredOperations
- Get Account Balancesget · Fetch buying power, cash, equity, margin, P&L, and optional top margin contributors for an account. Use this for account value, available cash, margin capacity, or buying-power questions.Clear StreetClear StreetPluginrequiredFinance
- Get Account Positionsget · List current positions for an account, including quantities, market value, and P&L. Use this for holdings or exposure questions. instrument_ids is a JSON array of OEMS UUIDs or symbols; resolve ambiguous symbols with search_instruments first.Clear StreetClear StreetPluginrequiredFinance
- Get All Instrument Eventsget · List earnings, dividends, stock splits, and IPO events across instruments. Use event_types, date range, sectors, and instrument_ids filters to narrow results.Clear StreetClear StreetPluginrequiredFinance
- Get Clockget · Fetch the current api-gw server clock in UTC. Use this before interpreting relative dates or checking whether market data is fresh.Clear StreetClear StreetPluginrequiredFinance
- Get Instrument Analyst Reportingget · Fetch analyst consensus, rating distribution, and price-target data for one instrument by OEMS UUID or exact symbol.Clear StreetClear StreetPluginrequiredFinance
- Get Instrument Balance Sheetsget · Fetch balance sheet statements for one instrument by OEMS UUID or exact symbol, with optional filing-date range and pagination.Clear StreetClear StreetPluginrequiredFinance
- Get Instrument By Idget · Fetch detailed instrument reference data by instrument identifier or exact symbol. Set include_options_expiry_dates=true when the user needs available option expirations.Clear StreetClear StreetPluginrequiredFinance
- Get Instrument Cash Flow Statementsget · Fetch cash flow statements for one instrument by OEMS UUID or exact symbol, with optional filing-date range and pagination.Clear StreetClear StreetPluginrequiredFinance
- Get Instrument Eventsget · Fetch earnings, dividend, split, and related event history for one instrument by OEMS UUID or exact symbol.Clear StreetClear StreetPluginrequiredFinance
- Get Instrument Fundamentalsget · Fetch supplemental fundamentals and company profile data by instrument identifier or exact symbol. Use this for market cap, P/E, dividend yield, beta, industry, sector, logo, or company description.Clear StreetClear StreetPluginrequiredFinance
- Get Instrument Income Statementsget · Fetch income statements for one instrument by OEMS UUID or exact symbol, with optional filing-date range and pagination.Clear StreetClear StreetPluginrequiredFinance
- Get Instrumentsget · List instruments with filters for type, borrow, margin, restrictions, and IDs. Use search_instruments for free-text lookup; use get_option_contracts for option chains.Clear StreetClear StreetPluginrequiredFinance
- Get Market Data Daily Summaryget · Fetch the latest daily OHLV summary for one or more instruments. instrument_ids is required and accepts a JSON array of OEMS UUIDs or symbols; use this for daily open, high, low, volume, and trade_date.Clear StreetClear StreetPluginrequiredFinance
- Get Market Data Snapshotget · Fetch current L1 market data snapshots, including quote, last trade, and session change fields. instrument_ids is a JSON array of OEMS UUIDs or symbols; use search_instruments first for company names or ambiguous symbols.Clear StreetClear StreetPluginrequiredFinance
- Get Market Hoursget · Fetch US equities/options market hours, current session status, and next session schedules. Use date as YYYY-MM-DD; omit market to return all supported market types.Clear StreetClear StreetPluginrequiredFinance
- Get Newsget · Fetch news items with optional time range, publisher, type, text search, instrument, and sector filters. Use from/to as YYYY-MM-DD or RFC3339 datetimes; array filters should be JSON arrays in MCP arguments.Clear StreetClear StreetPluginrequiredFinance
- Get Option Contractsget · List option contracts for one underlier with optional expiration, call/put, strike, and pagination filters. Use this to discover valid option instruments before market-data or trading calls.Clear StreetClear StreetPluginrequiredFinance
- Get Order By Idget · Fetch one order for an account by engine order ID or client order ID. Use an id or client_order_id returned by get_orders or a prior write-tool result.Clear StreetClear StreetPluginrequiredFinance
- Get Ordersget · List current and historical orders for an account. Use this for open orders, filled/canceled/rejected orders, queued or pending orders, and status checks. status and instrument_ids accept JSON arrays in MCP arguments.Clear StreetClear StreetPluginrequiredFinance
- Get Portfolio Historyget · Fetch daily portfolio history for an account over a YYYY-MM-DD date range. Use this for historical equity, realized/unrealized P&L, day P&L, and net P&L.Clear StreetClear StreetPluginrequiredFinance
- List Accountslist · List the trading accounts available to the user, with names, types, and whether each account is trading-enabled for this connection. Call this first when the user has multiple accounts or before any trading tool, then pass the chosen account_id to account-scoped tools.Clear StreetClear StreetPluginrequiredFinance
- Screen Instrumentsscreen · Screen the instrument universe with structured filters, sorts, and column selection over fundamentals, analyst, and liquidity fields (e.g. market_cap, price_to_earnings_ttm, dividend_yield_ttm, consensus_rating, consensus_price_target, volume, avg_volume_1m, sector). Use this for universe screens like 'liquid large caps with low P/E' instead of hand-picking symbols, then feed returned instrument IDs into market-data, events, or trading tools.Clear StreetClear StreetPluginrequiredFinance
- Search Instrumentssearch · Search instruments by symbol, alternate identifier, or company name. Use this before tools that require instrument IDs when the user gives a company name, partial symbol, CUSIP, ISIN, OPRA root, or otherwise ambiguous security reference.Clear StreetClear StreetPluginrequiredFinance
- check-syntheia-document-readycheck · Check whether a Syntheia document has finished indexing.
Call this after register_document until it reports the document is ready,
then you can ask questions about it with search_provisions.
Args:
doc_id: The document ID returned by register_document.
Returns:
A status string: "ready", "still_indexing", or "failed: <reason>".
If not found in the workspace, returns "not_found".SyntheiaSyntheiaPluginrequiredOperations
- create-syntheia-instant-reportcreate · Redline two .docx documents and return the result as a DOCX file.
WHEN TO CALL THIS TOOL — ALWAYS call it when a connected user identifies two
DOCX documents and asks to compare, redline, diff, tell the difference, show
what changed, or mark up the differences. Do not substitute document search
or provision retrieval. Each document may independently be an uploaded file,
a workspace title, or a workspace document ID, in any combination. Do not
call this tool if either document is known not to be DOCX.
For workspace documents, pass the two titles the user named; do not ask the
user for document IDs. This tool resolves each title to its document ID.
Titles may be exact or partial and are matched case-insensitively, but each
must identify exactly one document. If the user just copied two titles from
list-syntheia-documents, pass them as benchmark_title and target_title.
Each side must use exactly one source: its uploaded document or its workspace
title. Uploaded files must be .docx. The benchmark is the reference (e.g.
the standard template); the target is the document being checked against it.
The comparison runs upstream and can take several minutes on large
documents.
Args:
benchmark_document: An uploaded reference .docx. Omit when using a title.
target_document: An uploaded target .docx. Omit when using a title.
benchmark_title: Title (or doc_id) of the workspace reference document.
target_title: Title (or doc_id) of the workspace target document.
Returns:
The redlined .docx file as an embedded resource, with tracked changes.SyntheiaSyntheiaPluginrequiredOperations
- create-syntheia-workspacecreate · Create a new Syntheia workspace.
Args:
name: Display name for the new workspace.
workspace_type: Workspace type. Defaults to "SEARCH".
language: Primary language for the workspace. Defaults to "english".
Returns:
A string containing the new workspace_id.SyntheiaSyntheiaPluginrequiredOperations
- get-syntheia-current-workspaceget · Get the workspace this session is currently operating on.
This is whatever every other tool (search_provisions, list_documents,
prepare_upload, register_document, check_document_ready, ...) is already
implicitly using — set at login from the OAuth access token's
workspace_id claim, or overridden for this session by set_workspace.
Call this whenever the user asks which workspace they're currently in,
instead of guessing or asking them to disambiguate.
Returns:
The active workspace's id and name.SyntheiaSyntheiaPluginrequiredOperations
- get-syntheia-document-tagsget · Look up the tags assigned to ONE specific document, grouped by category.
Use this whenever the question asks for a document's METADATA VALUE under
ANY tag category — every workspace has these default categories: Author,
Document Type, Clause Type, Client, Party, Matter Number, Practice Group,
Sector, Jurisdiction, Document Date, Endorsed. If the question names a
specific document and asks what its value is under any of these
categories (e.g. "what Practice Group is X under", "what's the Matter
Number for Y", "what Sector is Z in", "what Client is this for"), call
this tool.
Use `list_documents_by_tag` / `search_provisions` instead when the question
goes the other way: finding documents BY a tag or category value (e.g.
"what documents have the Party tag Colab", "documents under Jurisdiction
good").
`search_provisions` can never answer a "what tag does document X have"
question for ANY of the categories above — it only searches clause text,
and a tag's value (e.g. Author = "Mahmoud") lives in document metadata,
not the document body. This tool reads that metadata directly instead of
searching text.
Args:
document: The document's title (exact or partial, case-insensitive)
or its doc_id.
Returns:
Tags grouped by category for the matched document(s), separating
confirmed tags from ML-predicted (unconfirmed) suggestions, or a
message if no document matches.SyntheiaSyntheiaPluginrequiredOperations
- get-syntheia-index-jsonget · Step 1 of the index-navigation approach: fetch ONE document's full
structural index (headings, snippets, keywords, and forward/reverse
cross-reference links by clauseId — no clause text yet) so YOU (or a
subagent) can pick which of its clauses to fetch.
The doc_id is resolved before this is called — a document confirmed by
name against list-syntheia-documents, or one member of a document group
the user picked (see server instructions' SCOPE RESOLUTION) — this tool
does not run its own search, it only fetches the index for the doc_id
you give it. Always returns exactly one document's index, never
combined with any other document's, so a single call's response size is
bounded no matter how many documents are in scope.
Before fanning this out across 2 or more documents, call
list-syntheia-documents(doc_ids=<every doc_id in scope>) — do not sum
word counts or compare them to the cap yourself. This applies whenever
2+ doc_ids are about to be navigated together for one task, however
scope was resolved: a GROUP the user picked from a clustered list,
several specific documents the user named directly (e.g. "cross-check
the charter, the underwriting agreement, and the prospectus"), or a mix
of both — it is not limited to the GROUP case. That call appends a
deterministic NAVIGATE-vs-VECTOR-SEARCH verdict computed from the
aggregate word count across every doc_id given: NAVIGATE means fan out
this way (once per document, then one merged get-syntheia-index-provisions
call); VECTOR SEARCH means per-document navigation isn't worth it
regardless of question shape — use search-syntheia-provisions with a
drafted HyDE passage instead, and discard any hit whose document isn't
in scope. If you intend to fan the NAVIGATE branch out across one
subagent per document, run this check yourself BEFORE spawning any of
them — a subagent that only ever sees its own doc_id cannot compute the
aggregate or apply this gate on your behalf. Do not skip this check
because the connect-time server instructions describing it may have
been truncated in your context — this paragraph is the backstop copy of
that rule.
Args:
doc_id: The document's doc_id, already resolved via
list-syntheia-documents.
Returns:
Selection-strategy instructions followed by this document's raw
index JSON wrapped in <index doc_id="..." title="..."> tags.SyntheiaSyntheiaPluginrequiredOperations
- get-syntheia-index-provisionsget · Step 2 of the index-navigation approach: given the clauseIds selected
from one or more get-syntheia-index-json calls, expand them by one level
of cross-references and fetch verbatim text, so you can answer the
question.
Only call this after get-syntheia-index-json — it does not run its own
search, it only fetches the clauses you specify.
Call this exactly ONCE per question, with the FULL merged selection
across every document/subagent — never once per document. `nodes` must
include every clauseId selected anywhere; do not drop any or trim down
to "the best few" before calling this. This applies even when the
question is a survey or enumeration across many documents (e.g. "what
types of X are defined across these documents") and the eventual answer
will look like a short list of names rather than quoted prose — the
list still has to be built from this call's verbatim text, not from
get-syntheia-index-json's titles/snippets. A large merged `nodes` list
(tens or low hundreds of entries) is not a reason to skip this call,
split it into several smaller calls, or fall back to answering from the
index instead.
Args:
nodes: The clauses to fetch, as a list of {"doc_id": ..., "node_id":
...} objects — node_id is the `clauseId` from the index. Pass
the complete merged selection across all documents/subagents.
Returns:
A "[Retrieval summary]" block (selection/match counts including the
real total clause count for the document(s) selected from, a
per-document breakdown, and a Source clauses deep link, like
search-syntheia-provisions'), answer instructions, then the
verbatim provision text (with cross-references automatically added)
wrapped in <provisions>...</provisions>, tagged per-clause with
"[doc=..., clause_id=..., link=...]" — link is a clickable deep link
to that individual clause, not just the aggregate "Source clauses:"
line. Answer the question directly from this — no further LLM call
is made by this tool.SyntheiaSyntheiaPluginrequiredOperations
- get-syntheia-workspaceget · Get details for a specific Syntheia workspace.
Args:
workspace_id: The numeric workspace ID.
Returns:
Workspace details including name, language, clause count, and document limit.SyntheiaSyntheiaPluginrequiredOperations
- list-syntheia-documentslist · List documents in the configured Syntheia workspace.
Args:
doc_ids: Optional — restrict the listing to exactly these doc_ids,
e.g. a document GROUP the user picked after you clustered this
tool's unfiltered output by title (see server instructions'
SCOPE RESOLUTION). When 2 or more doc_ids are given, the
result also ends with a deterministic NAVIGATE-vs-VECTOR-SEARCH
verdict computed from the group's aggregate word count (the
MULTI-DOCUMENT SIZE GATE) — do not sum word counts or compare
them to the cap yourself, this call does it for you, and that
verdict is authoritative once returned. Omit to list every
document in the workspace.
Returns:
A formatted list of documents with their doc_id, title, status, and
word count — use word count to gauge how large a document is. When
`doc_ids` narrows the listing to 2+ documents, ends with a
deterministic size verdict for that group.SyntheiaSyntheiaPluginrequiredOperations
- list-syntheia-documents-by-taglist · List documents in the workspace that have ANY of the given tags.
Tag names are matched case-insensitively against the workspace's tag list
(not full-text search — the name must match an existing tag). A document
is included if it carries at least one of the given tags.
A name may also be a tag CATEGORY rather than a specific value — every
workspace has these default categories: Author, Document Type, Clause
Type, Client, Party, Matter Number, Practice Group, Sector, Jurisdiction,
Document Date, Endorsed. Passing a category name (e.g. "Jurisdiction")
expands to every tag under it, matching any document tagged with any
value in that category — use this when the user names the category but
not a specific value (e.g. "documents with a Practice Group tag").
Args:
tag_names: One or more tag names OR category names to filter by,
e.g. ["NDA", "Contract"] or ["Jurisdiction"].
Returns:
A formatted list of matching documents, or a message naming any tags
that could not be resolved. When 2 or more documents match, ends
with a deterministic NAVIGATE-vs-VECTOR-SEARCH verdict computed from
their aggregate word count (see server instructions' RETRIEVAL
ROUTING) — do not sum word counts or compare them to the cap
yourself, this call does it for you.SyntheiaSyntheiaPluginrequiredOperations
- list-syntheia-workspaceslist · List all Syntheia workspaces accessible to this API key.
Returns:
A formatted list of workspaces with their workspace_id, status, name, and language.SyntheiaSyntheiaPluginrequiredOperations
- prepare-syntheia-uploadprepare · Obtain a presigned MinIO URL so that a client application can upload a file directly to storage.
WHEN TO CALL THIS TOOL — call it whenever the user wants to upload, ingest,
add, import, index, or load a file into Syntheia. Trigger phrases include:
"upload this file", "add this document", "ingest this contract", "load this
PDF", "index this agreement", "add to the workspace", "read this file".
This tool is intended for programmatic clients (e.g. a web app), NOT for the
LLM itself — the caller must compute an MD5 hash and perform an HTTP PUT,
which an LLM cannot do. Do not attempt to call this tool interactively.
If a document with this title already exists, returns its doc_id immediately
and no upload is needed. Otherwise returns a presigned URL and a storage key
for the caller to use.
Caller workflow after a successful response:
1. PUT the file binary to presigned_url (no auth headers,
Content-Type: application/octet-stream)
2. Call register_document with file_name, file_hash, title, file_extension
If the PUT fails for any reason (network restriction, blocked host, etc.),
do NOT retry. Instead, tell the user they can upload the file directly via
the Syntheia web interface at the web_upload_url included in the response.
Args:
title: Display title for the document in Syntheia.
file_hash: MD5 hex digest of the file (computed by the caller).
Returns:
JSON with presigned_url, file_name, and web_upload_url,
or {"exists": true, "doc_id": "..."}.SyntheiaSyntheiaPluginrequiredOperations
- register-syntheia-documentregister · Register a document that has already been uploaded to storage.
Call this after successfully PUT-ing the file binary to the presigned_url
returned by prepare_upload.
Returns immediately with a doc_id — indexing happens asynchronously.
Do NOT automatically call check_document_ready after this; let the user
decide when to check.
Args:
file_name: Storage key returned by prepare_upload.
file_hash: MD5 hex digest of the file (same value passed to prepare_upload).
title: Display title for the document.
file_extension: File type without leading dot, e.g. "pdf", "docx", "txt".
Returns:
A string containing the doc_id, e.g. "doc_id: abc123"SyntheiaSyntheiaPluginrequiredOperations
- search-syntheia-provisionssearch · Vector (semantic) search + cross-encoder rerank over document body text,
to answer a question about clauses, terms, obligations, dates, or any
other content actually written in a document.
Runs a 4-step retrieval pipeline (vector search, cross-encoder rerank,
cross-reference expansion, verbatim text fetch) and returns clause text.
Answer the question from that text — no separate LLM call is made by
this tool.
WHEN TO CALL:
- Similarity / text-block search — the user supplies a passage or
clause and asks for similar or matching text elsewhere in the
workspace. This is the direct entry point for that case; skip the
index tools entirely.
- Q&A — for ordinary questions ("what does the contract say", "what
are the payment terms", "what is the notice period", "does the
document allow X", "summarise the agreement"), the DEFAULT first
step is get_index_json/get_index_provisions instead. Call this
tool for Q&A only if, having seen the index, you judge vector
search fits better than structural navigation, OR as a
supplementary search run alongside get_index_json for requests
that are neither clean Q&A nor a similarity search.
Always retrieve via one of the two paths above before answering from
general knowledge.
WHEN NOT TO CALL — this tool only searches document BODY TEXT; it cannot
read a document's tags. If the question asks for a document's metadata
VALUE under a tag category (e.g. "who is the author of X", "what
jurisdiction is X under", "what practice group is Y"), call
`get_document_tags` instead — that value lives in the document's tags,
not its text, and this tool cannot retrieve it.
SCOPING WITH tag_names — narrow the search instead of scanning the whole
workspace whenever the question names a tag category or value. Every
workspace has these default categories: Author, Document Type, Clause
Type, Client, Party, Matter Number, Practice Group, Sector, Jurisdiction,
Document Date, Endorsed.
- Check first whether the question names one of these categories (e.g.
"documents under Jurisdiction") — pass the category name and it
expands to every tag under it.
- If the question also gives a specific value (e.g. "tagged NDA", "Party
Colab"), pass that value instead/as well — it matches that exact tag.
- A document is in scope if it has ANY of the resolved tags (OR, not
AND). Omit `tag_names` to search the whole workspace.
Step 1 — Vector search: candidates workspace-wide by embedding similarity,
paging in more while results stay in the same relevance tier as the best match.
Step 2 — Cross-encoder rerank: keeps the highest-precision nodes in the
same relevance tier as the best match, across a diverse set of documents.
Step 3 — Cross-reference expansion: adds clauses referenced by the selected clauses.
Step 4 — Batch text fetch: verbatim text for the full expanded clause set.
ANSWER POLICY:
- Answer EXCLUSIVELY from the verbatim text returned by this tool —
never from training knowledge or general expertise.
- If the retrieved provisions don't contain enough information, say:
"The documents in this workspace do not contain enough information to
answer this question."
- Cite the source document (doc_id) for every claim.
- After calling this tool, always include the "[Retrieval summary]"
block verbatim, unchanged, at the end of your reply — every time,
regardless of whether you found an answer or said there's not enough
information.
Args:
question: For direct similarity/text-block search, the user's
supplied passage or question, VERBATIM — do not paraphrase,
substitute synonyms, expand into domain/legal jargon, or reword
it before searching, even if you believe a reworded version
would retrieve better. For the Q&A-routing fallback case (see
server instructions' RETRIEVAL DECISION TREE / HYDE sections —
reached once a document group is too large to navigate, or
scope is the whole workspace/unknown), pass a Hypothetical
Document Embedding (HyDE) passage instead: a short passage
(1-3 sentences) drafted the way an answer would actually read
inside a document, not the literal question. Either way, call
this tool at most once per question — never call it again with
a different phrasing of the same question to refine or expand
the search; if the result seems thin, try tag_names or a
different tool instead of rewording.
tag_names: Optional tag names and/or category names to restrict the
search to documents carrying any of them, e.g. ["NDA"] or
["Jurisdiction"].
Returns:
Raw retrieval material, NOT a finished answer — you must compose the
answer yourself from this text (see Answer policy above): verbatim
provision text from the matched clauses, followed by a retrieval
summary (including the workspace name) and a link to view the
source clauses in the Syntheia web app. If a requested tag name
doesn't match any existing tag or category, returns a message
saying so instead of silently searching the whole workspace.SyntheiaSyntheiaPluginrequiredOperations
- set-syntheia-workspaceset · Switch the active workspace for the rest of this session.
Every other tool that operates on "the workspace" (search_provisions,
list_documents, prepare_upload, register_document, check_document_ready)
uses whatever workspace this points at, until it is called again or the
server restarts. Use list_workspaces to find the workspace_id first.
Args:
workspace_id: The numeric workspace ID to switch to.
Returns:
Confirmation with the new workspace's name.SyntheiaSyntheiaPluginrequiredOperations
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.