Skip to main content
Glama
Sign In

Well

by io.github.WellApp-ai
OverviewDiscussionsAdmin

Retired: use well_create_declaration_filing

well_create_vat_filing
Read-only

Retired, runs nothing. Prepare the return with well_prepare_vat_return, then, after the person answered its figures, call well_create_declaration_filing with declaration_type "fr-vat-ca3" and the same document_id. Well fills the return in the person's Chrome and stops before the send: the person clicks it on the tax site.

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • removedInput schema / properties / document_id
      Removed value: -{
-  "description": "The `document_id` well_prepare_vat_return returned for this return, in this conversation. Never a figure.",
-  "format": "uuid",
-  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-  "type": "string"
-}
    • removedInput schema / properties / idempotency_key
      Removed value: -{
-  "description": "Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.",
-  "maxLength": 255,
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / run_in_background
      Removed value: -{
-  "const": true,
-  "description": "Always true: the person's own message explicitly asked Well to file in the background (« en tâche de fond », « in the background »). Without that ask, do not call this tool.",
-  "type": "boolean"
-}
    • removedInput schema / properties / workspace_id
      Removed value: -{
-  "description": "Target 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.",
-  "format": "uuid",
-  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-  "type": "string"
-}
    • removedInput schema / properties / workspace_scope
      Removed value: -{
-  "description": "Restrict 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.",
-  "enum": [
-    "family"
-  ],
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "document_id",
-  "run_in_background"
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "conversation_id": {
-      "description": "The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.",
-      "type": "string"
-    },
-    "conversation_id_note": {
-      "description": "Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.",
-      "type": "string"
-    },
-    "conversation_id_source": {
-      "description": "Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.",
-      "enum": [
-        "host_meta",
-        "argument",
-        "minted"
-      ],
-      "type": "string"
-    },
-    "error": {
-      "type": "string"
-    },
-    "message": {
-      "type": "string"
-    },
-    "newly_connected": {
-      "description": "Tools 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.",
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "name": {
-            "type": "string"
-          },
-          "service_id": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "name",
-          "service_id"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "period": {
-      "additionalProperties": false,
-      "properties": {
-        "from": {
-          "type": "string"
-        },
-        "to": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "from",
-        "to"
-      ],
-      "type": "object"
-    },
-    "refusal": {
-      "enum": [
-        "no_workspace",
-        "inactive_workspace",
-        "no_person",
-        "not_from_whatsapp",
-        "unknown_return",
-        "already_filed",
-        "filing_live",
-        "period_already_filed",
-        "not_validated",
-        "not_fileable",
-        "return_changed",
-        "prior_credit_unconfirmed",
-        "login_missing",
-        "run_live",
-        "cloud_unavailable",
-        "filing_off",
-        "failed"
-      ],
-      "type": "string"
-    },
-    "resolved_workspace": {
-      "additionalProperties": false,
-      "description": "The workspace that answered, when the caller named none and the token authorizes several.",
-      "properties": {
-        "name": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "workspace_id": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "workspace_id",
-        "name"
-      ],
-      "type": "object"
-    },
-    "runner": {
-      "enum": [
-        "paired_chrome",
-        "cloud"
-      ],
-      "type": "string"
-    },
-    "site": {
-      "type": "string"
-    },
-    "success": {
-      "type": "boolean"
-    },
-    "vat_credit": {
-      "maximum": 9007199254740991,
-      "minimum": -9007199254740991,
-      "type": "integer"
-    },
-    "vat_due": {
-      "maximum": 9007199254740991,
-      "minimum": -9007199254740991,
-      "type": "integer"
-    }
-  },
-  "required": [
-    "success"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changed
    • changedOutput schema / properties / refusal / enum
      Previous value: -[
-  "no_workspace",
-  "inactive_workspace",
-  "no_person",
-  "not_from_whatsapp",
-  "unknown_return",
-  "already_filed",
-  "filing_live",
-  "period_already_filed",
-  "not_validated",
-  "not_fileable",
-  "return_changed",
-  "login_missing",
-  "run_live",
-  "cloud_unavailable",
-  "filing_off",
-  "failed"
-]New value: +[
+  "no_workspace",
+  "inactive_workspace",
+  "no_person",
+  "not_from_whatsapp",
+  "unknown_return",
+  "already_filed",
+  "filing_live",
+  "period_already_filed",
+  "not_validated",
+  "not_fileable",
+  "return_changed",
+  "prior_credit_unconfirmed",
+  "login_missing",
+  "run_live",
+  "cloud_unavailable",
+  "filing_off",
+  "failed"
+]
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description confirms there are no side effects ('runs nothing'), which is consistent. It also discloses the downstream flow (Chrome-filled, stops before the person clicks send), though that describes the replacement tool, an ambiguity that could momentarily mislead about this call's effects.

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?

The critical information, 'Retired, runs nothing', is front-loaded in the first clause, and the migration instructions are compact. The final sentence describes the successor's UI behaviour, which is useful for the migration but is the least essential part.

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

Completeness4/5

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

For a retired no-op with full schema coverage, no output schema, and safe annotations, the description supplies everything needed: it does nothing, and here is the exact call to make instead. Explicitly saying 'do not invoke this tool' would close the last small gap.

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

Parameters3/5

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

Schema coverage is 100% on the single conversation_id parameter, so the baseline applies. The description mentions document_id and declaration_type, but those belong to well_create_declaration_filing, not to this tool's schema, so it adds no real semantics for the parameter an agent actually passes here.

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

Purpose4/5

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

The opening clause 'Retired, runs nothing' is unambiguous about what this tool does (a no-op) and names the exact successor, well_create_declaration_filing, with its declaration_type. The only weakness is that most of the remaining text describes the successor's behaviour rather than this tool's, so the split between 'this does nothing' and 'that does the work' takes a moment to parse.

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?

It gives an explicit replacement path: prepare with well_prepare_vat_return, then call well_create_declaration_filing with declaration_type "fr-vat-ca3" and the same document_id. That is a concrete when-to-use-the-alternative instruction with the arguments spelled out, leaving nothing to inference.

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

All Well toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources