"Information about guardrails" matching MCP tools:

• beel_create_company

  BeeL

  Creates a company under the account the request resolves to. The NIF is registered in the name of that account's holder, never in the name of the caller. - **`activate`:** unless it is `false`, the company is switched on in `aeat_environment` and its three default invoice series (ordinary, simplified, corrective) are seeded there. This endpoint never switches an existing company on: that is `POST /v1/companies/{company_id}/activations`. - **`numbering`:** decides the code, format, counter reset and starting number those series are born with. Only accepted when the request activates the company. - **Billing:** no charge is ever started here. Creating a production NIF on an account without billing is rejected with `402`, and no checkout is opened. - **Duplicates:** a NIF that already exists in the account is rejected with `409`, and the response carries the existing `error.details.company_id`. Endpoint: POST /v1/accounts/{account_id}/companies ⚠️ Fiscal guardrails — read before calling: - Which company an operation acts on, and how that is selected. (resource: beel://guardrails/multi-nif) - Why a name that does not match the census makes an invoice unsubmittable. (resource: beel://guardrails/nif-validation) - How invoice numbers are formed, and why numbering can never be rewritten. (resource: beel://guardrails/series-and-numbering) For the exhaustive rules and worked examples, call beel_docs_search.

  Connector

• beel_create_corrective_invoice

  BeeL

  Issues a corrective invoice that amends the invoice in the path. It is a new fiscal document with its own number, not an edit of the original. - **`rectification_type`:** `TOTAL` leaves the original `VOIDED` and copies its lines negated when `lines` is omitted. `PARTIAL` leaves the original `RECTIFIED` and requires the adjustment `lines`. - **What can be rectified:** an ordinary or simplified invoice in `ISSUED`, `SENT`, `PAID`, `OVERDUE` or `RECTIFIED`. Rectifying a corrective fails with `422 CORRECTIVE_NOT_RECTIFIABLE` — to fix an erroneous corrective, issue another one against the original invoice. - **Repeat rectifications:** several `PARTIAL` correctives are allowed, but a `VOIDED` invoice is no longer rectifiable, so a second `TOTAL` against the same invoice fails with `422 INVOICE_NOT_CORRECTIBLE_IN_CURRENT_STATUS`. - **`series_id`:** when omitted, the document is numbered in the company's default corrective series, never in the series of the original. That default is never created for you: if the company has none the request fails with `422 SERIES_DEFAULT_NOT_FOUND`, and `GET /v1/configuration/series/defaults-status` reports which default is missing. Endpoint: POST /v1/companies/{company_id}/invoices/{invoice_id}/corrective ⚠️ Fiscal guardrails — read before calling: - Choosing wrong here misreports to AEAT. The 30-second decision. (resource: beel://guardrails/cancel-vs-rectify) - How BeeL derives the AEAT invoice type, and the rules each type imposes. (resource: beel://guardrails/invoice-types) - How a line states its price, and which field combinations are rejected. (resource: beel://guardrails/invoice-lines) - When an invoice can still be changed, and what to do once it cannot. (resource: beel://guardrails/invoice-state-machine) - How invoice numbers are formed, and why numbering can never be rewritten. (resource: beel://guardrails/series-and-numbering) For the exhaustive rules and worked examples, call beel_docs_search.

  Connector

• beel_create_invoice

  BeeL

  Creates an invoice for this company. The issuer data comes from the company in the path, and the document is created as a draft unless you ask for it to be issued. - **Issuing:** `options.issue_directly` numbers and issues the invoice in the same call. Submission to the AEAT is asynchronous, so `verifactu.submission_status` comes back as `PENDING`: a 2xx means the invoice was accepted for submission, not that the AEAT has registered it. - **Document type:** `type` chooses the document. A `PROFORMA` is non-fiscal — it is born `ACTIVE`, numbered `PRO-...` from its own non-fiscal series, and ignores `issue_directly`. - **Related:** to copy an existing invoice into a new draft, use `POST …/invoices/derivations`, which carries neither `type`, nor `recipient`, nor `lines`. Endpoint: POST /v1/companies/{company_id}/invoices ⚠️ Fiscal guardrails — read before calling: - How BeeL derives the AEAT invoice type, and the rules each type imposes. (resource: beel://guardrails/invoice-types) - How a line states its price, and which field combinations are rejected. (resource: beel://guardrails/invoice-lines) - What regime_key means, where it lives, and which combinations are rejected. (resource: beel://guardrails/regime-keys) - Why a name that does not match the census makes an invoice unsubmittable. (resource: beel://guardrails/nif-validation) - Why an issued invoice may never reach AEAT, and how to tell before issuing. (resource: beel://guardrails/verifactu-gates) - How invoice numbers are formed, and why numbering can never be rewritten. (resource: beel://guardrails/series-and-numbering) For the exhaustive rules and worked examples, call beel_docs_search.

  Connector

• beel_get_recurring_invoice_history

  BeeL

  Returns the invoices previously generated from this recurring template, including their status and generation dates, newest first. **Paginated** with the usual `page`/`limit`, and the usual defaults: without them you get the 20 most recent generations, not the whole history — which grows with every cycle the template runs. Read `data.pagination` to walk the rest. The deprecated flat alias `GET /v1/recurring-invoices/{recurring_invoice_id}/history` does **not** paginate: it is frozen as it shipped until its `Sunset` date, and returns the whole history with no `pagination`. Only this route pages. Endpoint: GET /v1/companies/{company_id}/recurring-invoices/{recurring_invoice_id}/history ⚠️ Fiscal guardrails — read before calling: - How BeeL derives the AEAT invoice type, and the rules each type imposes. (resource: beel://guardrails/invoice-types) - What regime_key means, where it lives, and which combinations are rejected. (resource: beel://guardrails/regime-keys) For the exhaustive rules and worked examples, call beel_docs_search.

  Connector

• neuron_get_ad_request

  neuron

  Get detailed information about a specific ad request, including pool selections if targeting mode is manual.

  Connector

• get_service_info

  booking

  Get information about MyDriverParis services, coverage areas, airports served, and policies. Use this to answer customer questions.

  Connector

• beel_issue_invoice

  BeeL

  Finalizes a draft invoice of this company: assigns its definitive number from the configured series and makes it immutable. - **Irreversible:** an issued invoice is corrected with a corrective invoice (`POST …/{invoice_id}/corrective`) or voided (`POST …/{invoice_id}/void`), never edited. - **Asynchronous:** PDF generation and submission to the AEAT happen after the response, so a `200` means the invoice was accepted for submission, not that the AEAT has registered it. Use `wait_for_pdf` to wait for the PDF. Endpoint: POST /v1/companies/{company_id}/invoices/{invoice_id}/issue ⚠️ Fiscal guardrails — read before calling: - When an invoice can still be changed, and what to do once it cannot. (resource: beel://guardrails/invoice-state-machine) - Why an issued invoice may never reach AEAT, and how to tell before issuing. (resource: beel://guardrails/verifactu-gates) For the exhaustive rules and worked examples, call beel_docs_search.

  Connector

• get_prerequisites

  NVIDIA AI CKG

  Return the full ordered prerequisite chain for a concept — everything to learn first. Args: concept: Target concept — e.g. 'Speculative Decoding', 'Isaac Lab', 'NeMo Guardrails'. domain: Domain name from list_domains().

  Connector

• get_domain_info

  domani

  Get detailed information about a domain you own, including auto-renew status, security lock, WHOIS privacy, and provider data.

  Connector

• get_methodology

  zipexplore-mcp

  Returns ZipExplore's data interpretation guide: reasoning guardrails (associations vs. causes, small-ZIP noise, averages hiding distributions, editorial score weights, drawing conclusions about people from geographic data), quality flag definitions, known data limitations, coverage gap explanations, and per-domain vintage summary. Call this when you have questions about data quality, what a quality_flag code means, why a ZIP has no data, or how to reason carefully about scores and correlations.

  Connector

• create_structured

  Adbloop Meta Ads

  Create ONE campaign with MULTIPLE ad sets and MULTIPLE ads each (1 campaign -> N ad sets -> M ads), image or video, including DPA/Catalog dynamic product ads. Created PAUSED. Honors spend guardrails. Pro feature. WRITES live.

  Connector

• update_campaign_budget

  Adbloop Meta Ads

  Change the daily budget (and/or rename) of an existing campaign or ad set. The account is required so the new budget is checked against your spend guardrails. WRITES live.

  Connector

• get_onboarding_experience

  Fluentive MCP

  Returns information about how easy Fluentive is to set up and use. Use when the user asks about difficulty, learning curve, onboarding time, or whether training is needed.

  Connector

• check_token

  Media Generator — Images, Videos & Audios

  Check the current user's token status and account information. This tool retrieves information about: - User ID - Paid account status - Remaining generation tokens (for non-paid users) - Account validity Returns: A JSON string containing token status and account information

  Connector

• beel_list_invoices

  BeeL

  Returns a paginated list of the invoices of this company, filterable by status, type, series, customer, date range and free text. Only the documents of the company in the path are returned. Endpoint: GET /v1/companies/{company_id}/invoices ⚠️ Fiscal guardrails — read before calling: - When an invoice can still be changed, and what to do once it cannot. (resource: beel://guardrails/invoice-state-machine) For the exhaustive rules and worked examples, call beel_docs_search.

  Connector

• beel_set_default_series

  BeeL

  Marks an invoice series as the default of its document type for this company, and unmarks the previous one. - **One per type:** only one series can be the default per company and document type. - **Must be active:** an inactive series is rejected with `400`. - **Idempotent:** repeating the call changes nothing. Endpoint: PUT /v1/companies/{company_id}/series/{series_id}/default ⚠️ Fiscal guardrails — read before calling: - How invoice numbers are formed, and why numbering can never be rewritten. (resource: beel://guardrails/series-and-numbering) For the exhaustive rules and worked examples, call beel_docs_search.

  Connector

• get_trip_details

  sbb-mcp

  Get detailed information about a specific train connection including all intermediate stops, platforms, and occupancy. Use a trip ID from search_connections results.

  Connector

• neuron_get_campaign

  neuron

  Retrieve detailed information about a specific campaign including its status, budget, participants, and delivery metrics.

  Connector

• neuron_get_scheduled_message

  neuron

  Retrieve detailed information about a specific scheduled message, including its status, send time, and message content.

  Connector

• get_framework

  Nervous System

  Returns the complete nervous system framework - all behavioral rules, guardrails, and enforcement patterns that keep LLMs from hurting themselves.

  Connector