Skip to main content
Glama

Fill the tax declaration for the person to send

well_create_declaration_filing

Start the fill of one prepared tax declaration in the person's own Chrome, from their WhatsApp turn. Well opens the authority's site there, the person signs in themselves, Well types the boxes of the prepared declaration and stops before the send: the person checks the form and clicks Envoyer themselves. Use it only when the person's own message asks Well to fill or file the declaration, after the declaration was prepared.

Pass declaration_type and the document_id the prepare tool returned. Never pass an amount: Well reads the figures from the stored declaration and checks them again against the declaration's blocking checks, and the CA3 against the books too, on the basis it was prepared on. Never say the declaration is filed or sent. On success, outcome queued means nothing runs yet: never say the fill started, and word the reply from message. waits_for_extension: true means the person's Chrome has no Well extension that takes the fill yet: the fill starts by itself once they install or update it, with no new ask, and message says what to tell them.

On refusal: no_extension, the PDF already sent is the path, the person files it themselves. extension_outdated, the PDF already sent is the path, and an update of the Well extension lets Well fill the next one. return_changed, prepare the declaration again and show the new figures. not_fileable, the books still do not give the whole return. When it carries reasons, first say each one in plain words: for unstamped posted entries, each entry gets its company in the source ledger and is synced again before the filing; for no books company confirmed, the person confirms their company first. With no reasons, when the prepared draft listed gaps, say in plain words what to fix and fill nothing; with neither, prepare the declaration again and show the new figures, and give no advice to correct the ledger. prior_credit_unconfirmed, line 22 waits for the person: ask once what « le crédit reporté de ta déclaration précédente » was, naming no line, prepare the declaration again with the prior_credit_euros they give, and show the new figures. check_blocked, the declaration fails a blocking check listed in rule_ids: say what to correct and fill nothing. already_filed, never fill again. period_already_filed, say plainly it is filed on the date in filed_on (day/month). filing_live, another fill runs: start nothing. handed_over_pending, the filled form waits in the person's Chrome: tell them to send it from that tab. not_validated, show the prepared figures and ask the person to confirm them in a new message. confirmation_required, ask the one numbered question the error text gives and end the turn. Follow the error text for any other refusal.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
document_idYesThe `document_id` of the prepared declaration, as its prepare tool returned it in this conversation.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.
declaration_typeYesThe declaration to fill: `fr-vat-ca3` for the CA3 VAT return prepared by well_prepare_vat_return, `fr-micro-turnover` for the URSSAF micro-entrepreneur turnover declaration prepared by well_prepare_micro_declaration.

Output Schema

NameRequiredDescriptionDefault
codeNo
siteNo
errorNo
periodNo
messageNo
outcomeNo
reasonsNo
refusalNo
successYes
filed_onNo
rule_idsNo
launch_linkNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
declaration_typeNo
browser_action_idNo
browser_reachableNo
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
waits_for_extensionNo
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / refusal / enum
      Previous value: -[
      -  "no_workspace",
      -  "inactive_workspace",
      -  "no_person",
      -  "not_from_whatsapp",
      -  "declaration_type_not_ready",
      -  "unknown_return",
      -  "already_filed",
      -  "period_already_filed",
      -  "filing_live",
      -  "handed_over_pending",
      -  "not_validated",
      -  "not_fileable",
      -  "return_changed",
      -  "prior_credit_unconfirmed",
      -  "check_blocked",
      -  "check_unavailable",
      -  "untyped_content",
      -  "confirmation_required",
      -  "confirmation_declined",
      -  "no_extension",
      -  "extension_outdated",
      -  "skill_unavailable",
      -  "failed"
      -]New value: +[
      +  "no_workspace",
      +  "inactive_workspace",
      +  "no_person",
      +  "not_from_whatsapp",
      +  "declaration_type_not_ready",
      +  "unknown_return",
      +  "already_filed",
      +  "period_already_filed",
      +  "filing_live",
      +  "handed_over_pending",
      +  "not_validated",
      +  "not_fileable",
      +  "return_changed",
      +  "prior_credit_unconfirmed",
      +  "check_blocked",
      +  "check_unavailable",
      +  "untyped_content",
      +  "confirmation_required",
      +  "no_extension",
      +  "extension_outdated",
      +  "skill_unavailable",
      +  "failed"
      +]
  2. Changed2 schema fields changed
    • removedOutput schema / properties / resolved_workspace / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / resolved_workspace / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Changed1 schema field changed
    • addedOutput schema / properties / waits_for_extension
      Added value: +{
      +  "type": "boolean"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / declaration_type / description
      Previous value: -"The declaration to fill: `fr-vat-ca3` for the CA3 VAT return prepared by well_prepare_vat_return."New value: +"The declaration to fill: `fr-vat-ca3` for the CA3 VAT return prepared by well_prepare_vat_return, `fr-micro-turnover` for the URSSAF micro-entrepreneur turnover declaration prepared by well_prepare_micro_declaration."
  5. Added

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only mark this as a non-read-only, open-world, non-destructive write. The description adds what the annotations cannot: that the person signs in themselves, that Well stops before Envoyer, what 'queued' and waits_for_extension mean for reply wording, and a full refusal taxonomy with the required reply for each. No annotation is contradicted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one-sentence purpose before the reference material, and the refusal catalog is keyed by code so an agent can jump to the branch it received. It is still very long and dense, with some restatement of points already carried in schema descriptions, which keeps it just short of maximal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an open-world write with eleven distinct refusal outcomes and a hand-off to the person's browser, the description covers the prerequisites, the success-path wording rules, and every refusal branch. The output schema carries the return shape, so no space is wasted re-explaining it beyond the two outcome fields that change the reply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all six parameters, giving a baseline of 3. The description adds real constraints beyond it: never pass an amount, take document_id from the prepare tool's return, and the workspace_id conditionality — though it repeats rather than expands the declaration_type enum meanings.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it starts the fill of one already-prepared tax declaration in the person's own Chrome and stops before the send. The boundary against the prepare step and against a plain filing is explicit, so an agent can separate this from well_prepare_vat_return or well_create_vat_filing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('only when the person's own message asks Well to fill or file the declaration, after the declaration was prepared') and an explicit precondition on which declaration_type/document_id to pass. It also resolves the workspace question: call directly when the token authorizes one workspace, pass workspace_id when it authorizes several.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources