Well

Create tax rate

well_create_tax_rate

Create a tax-rate rule for the current workspace. Supply its name, rate and tax type. This defines a tax rule; it does not create an invoice or move money.

Input Schema

Name	Required	Description
`name`	Yes
`rate`	Yes
`country`	No
`tax_type`	Yes
`is_active`	No
`is_default`	No
`effective_to`	No
`workspace_id`	No	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.
`effective_from`	No
`conversation_id`	No	The 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_key`	No	Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
`workspace_scope`	No	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.
`collected_account_id`	No
`deductible_account_id`	No

Output Schema

Name	Required	Description
`code`	No
`data`	No
`error`	No
`success`	Yes
`reply_lines`	No
`conversation_id`	No	The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
`near_candidates`	No
`newly_connected`	No	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.
`conversation_id_note`	No	Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.
`conversation_id_source`	No	Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.
`near_candidates_truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 28, 2026

removedInput schema / properties / effective_from / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / effective_from / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / effective_to / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / effective_to / type
```
Added value: +[
+  "string",
+  "null"
+]
```
addedOutput schema / properties / code
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / data / properties / attributes / properties / country / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / data / properties / attributes / properties / country / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / data / properties / attributes / properties / effective_from / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / data / properties / attributes / properties / effective_from / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / data / properties / attributes / properties / effective_to / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / data / properties / attributes / properties / effective_to / type
```
Added value: +[
+  "string",
+  "null"
+]
```

addedOutput schema / properties / near_candidates

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "company_id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "company_id",
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / near_candidates_truncated
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / reply_lines

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

AddedOct 22, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, openWorld=false, so the safety profile is covered. The description adds the useful boundary that this does not create invoices or move money, but says nothing about permissions, duplicate-name behavior, or what is_default/is_active do in combination with existing rules.

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

Conciseness5/5

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

Two sentences, front-loaded with the action and scope, with zero filler. Every clause carries information.

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

Completeness2/5

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

For a 14-parameter mutation with low schema coverage, the description is too thin: it omits the meaning of effective_from/effective_to, country, default/active flags, and workspace targeting beyond 'current workspace'. Output schema exists, so return values need not be explained, but input-side semantics are largely missing.

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

Parameters2/5

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

Schema description coverage is only 29% across 14 parameters, and the description only restates the three required fields already declared in the schema's required list. Effectivity dates, country, is_default/is_active, and the collected/deductible account ids get no explanatory treatment in either place.

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?

States a specific verb and resource ('Create a tax-rate rule') and its scope ('for the current workspace'), and the required fields. It does not explicitly contrast with the sibling write tools well_update_tax_rate / well_delete_tax_rate, so sibling disambiguation is only implied by the verb.

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

Usage Guidelines3/5

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

Usage is implied by 'Create' versus the update/delete siblings, and one boundary is drawn ('does not create an invoice or move money'), which helps avoid misfires. But there is no explicit when-to-use/when-not-to-use guidance, no note on duplicate names or how this relates to well_update_tax_rate.

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

All Well tools Inspect

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

Need Help?