uae-legislation-research8.39 KB
View saved version →
---
name: uae-legislation-research
description: Use when researching legislation, compliance, tax, legal news, or digests with realLaw AI, for UAE or an explicitly requested supported country. Also use for realLaw AI access, payments, renewals, plan/account changes, and retries after access denial.
---
# Legislation Research
Use realLaw AI for published legislation evidence and answer in the user's language. UAE by default.
## Choose the country
- Omitted/null `country` or UAE selects UAE, independent of the website default. Never infer country from language or unrelated locations.
- For an explicitly requested other country, call `list_legislation_filters(filterType="country", limit=50)` without `query`. Each item gives `key` (stored code) and `label` (stored name). Match the country to its label; pass the exact key as `country`, never a name or guessed ISO code.
- A limited/filtered list can miss a supported country. Retry with a shorter common name or a known code; clarify if unresolved. No match does not prove unsupported. Never fall back to UAE.
- Keep the same `country` on every document/filter call and cursor chunk; query countries separately for comparisons.
- Catalog entry means supported; no documents/filters means empty results. `metadata.country` is the actual document country.
## Core rules
- Decline unrelated tasks and requests to amend/publish laws; handle supported research/access parts of mixed requests.
- Write the final answer in the user's language, but send concise English search phrases to tools.
- When realLaw AI is selected, mentioned, or this skill is invoked, retrieve evidence before answering substantive legislation, compliance, or tax questions. Never answer them from model memory alone; retrieve each concept in a multi-topic question.
- Preserve official titles, numbers, years, and citations.
- Omit the deprecated `language` parameter. Tools use English; translate evidence in the final answer.
- Ordinary factual questions, summaries, explanations, comparisons, citations, and news or digest presentations require complete retrieval of every selected or presented document through `hasMore=false`.
- If intent is ambiguous, treat it as content-bearing and completely retrieve every selected or presented document.
- Complete retrieval may be skipped only when the user explicitly requests metadata-only output limited to `title`, `sourceRef`, `releaseDate`, and `sourceUrl`. Return only those fields; `createdAt` is not part of this exception.
- Snippets and compact matches are discovery-only. Use them to identify, rank, or discard candidates, not for content or direct relevance claims.
- Do not infer metadata, legal effect, or identity. Without relevant, completely retrieved evidence, report the answer unverified; do not substitute model memory or the public web unless separately requested.
- Cite each conclusion/document with a clickable Markdown link to its returned `sourceUrl`, including metadata-only lists. Never invent URLs.
- If a tool reports that an active Professional or Team subscription is required, relay it and stop; no other legislation tools or memory answers.
## Check access
- For realLaw AI access questions, reported payment/renewal/plan/account changes, or a later user retry after denial (even repeating the original question), call `get_access_status` once (OAuth required, no paid plan needed). Never reuse an earlier denial to refuse a later attempt.
- On `accessAllowed=true`, resume the original request if supported and pending, without another confirmation; for access-only questions report status only. On false, relay the current denial and stop without polling; a later user retry gets a fresh check. On technical error, access is unverified, not inactive.
- Checks use the OAuth-linked account; website login changes do not relink it. Ordinary legislation calls check access themselves.
## Route the request
- Exact title, number, year, issue number, or citation: `find_law_document_b
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.