# Tools Adragent works through **tools** — the operations it can do for you. This page explains what a tool is and what falls inside (and outside) the catalog. {% hint style="info" %} **You do not pick tools.** You describe what you want; Adragent picks the tool that matches your intent. If your intent does not match any tool, Adragent says so before anything moves. {% endhint %} ## What a tool is A tool is one operation Adragent can perform. Each tool has: * A **name** that says what it does — *apply promotion*, *list properties*, *update rate plan*, *find places nearby*. * An **input** — what Adragent needs from you. Adragent extracts these from your request, or asks for what is missing. * An **output** — for read tools, the answer; for write tools, the preview, then on confirmation, the result. * A **confirmation level** — read tools run immediately; write tools always go through approval. * A **link to the right console page** — Adragent deep-links you to the relevant screen when it makes sense. *** ## Confirmation levels Each tool declares how it expects to be approved. The level is the platform's call, not Adragent's; the same operation has the same confirmation level for everyone. | Tool kind | What you do | | -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | | **Read** — list, search, view, summarise | Nothing. Adragent answers right away. | | **Write — small** — single record, non-critical fields | Reply *yes* in chat after the preview. | | **Write — critical** — bulk edits, rate or inventory cells, payment configuration, contract status | Click **Confirm** on a structured preview card. | | **Destructive — bulk** — wide-range deletes, full-organization changes | Click **Confirm** on the structured preview. The preview shows the full impact. | See [Confirm-before-apply](/console/adragent/confirm-before-apply.md) for the full pattern. *** ## What you can ask Adragent The catalog covers day-to-day operator work. Read coverage is the priority for new domains — every domain that lands in the console gets read tools first, with write tools added as their preview surfaces are designed. ### Properties and rooms *** `Read · Write` * List properties, find by location or attribute, open one. * Create a new property, update an existing one, restore a removed one. * List rooms in a property, open a room, create / update / remove a room. Open the [catalog reference](/console/catalog/property.md) [→](/console/catalog/property.md) *** ### Rates, inventory and promotions *** `Read · Write` * List rate plans, open one, update, apply a rate change. * Read inventory, update inventory, apply stop-sale (close a room or rate plan to new bookings for given dates), apply restrictions (min stay, day-of-week, advance purchase). * Apply a promotion, draft a discount. Open the [rate plan guide](/console/pricing-and-availability/rate-plans.md) [→](/console/pricing-and-availability/rate-plans.md) *** ### Distribution and channels *** `Read · Write` * List available channels, list per-property channel bindings, list connector credentials. * Publish a property to a channel, pause a channel push, check failed pushes. Open the [distribution overview](/console/distribution/overview.md) [→](/console/distribution/overview.md) *** ### Contracts and onboarding *** `Read · Write` * List contracts, open one, draft an onboarding from a forwarded email. * List allotments and release periods, draft a markup rule. Open the [contracts guide](/console/contracts-and-onboarding/contracts.md) [→](/console/contracts-and-onboarding/contracts.md) *** ### Mapping and curation *** `Read · Write` * List connector managers, list mapping sources, list attribute mappings, list meal-plan mappings. * Open a mapping, update it, queue an unmapped item for review. Open the [mapping reference](/console/mapping-and-curation/canonical-mapping.md) [→](/console/mapping-and-curation/canonical-mapping.md) *** ### Locations *** `Read · Write` * Search places, list places by type, find children of a place, find nearby places. * Resolve a map location, get / upsert a property's location. Open the [catalog reference](/console/catalog/property.md) [→](/console/catalog/property.md) *** ### Payments *** `Read · Write` * Read settlement, list virtual card transactions, list pending refunds, list chargeback status. * Issue a refund (with confirmation), prepare a reconciliation report. Open the [payments overview](/console/payments/overview.md) [→](/console/payments/overview.md) *** ### Catalog references and tags *** `Read-only` * List categories, list attributes, open one. * List tags, open one. Open the [catalog reference](/console/catalog/property.md) [→](/console/catalog/property.md) *** ### Documents *** `Read-only` * List documents, open one. Downloads happen in the console for security reasons. Open the [contracts guide](/console/contracts-and-onboarding/contracts.md) [→](/console/contracts-and-onboarding/contracts.md) *** ### Bookings and reports *** `Read-only` * List bookings, summarise by property, channel or date range. * Read operational metrics and operation history. Open the [activity log](/console/notifications-and-ops/audit-log.md) [→](/console/notifications-and-ops/audit-log.md) *** ## When something is not yet a tool If you ask Adragent to do something it cannot do, it tells you, plainly. You can: * **Use the console** for that operation — your manual fallback. * **Tell us.** The platform tracks tool-coverage gaps; the gap goes into the queue alongside the rest of the agent surface. {% hint style="warning" %} **Adragent does not bluff.** If the catalog cannot fulfil your intent, you find out before approving anything; the system blocks made-up operations from reaching execution. {% endhint %} ## Where to next * **The approval step in detail** → [Confirm-before-apply](/console/adragent/confirm-before-apply.md) * **The channels Adragent meets you on** → [Channels](/console/adragent/channels.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://adrasis.gitbook.io/console/adragent/tools.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.