Skip to main content
Glama

Well

by io.github.WellApp-ai
OverviewDiscussionsAdmin

Claim a statement dropped on the website

well_claim_statement_draft

Claim every bank statement the user dropped on Well's website in one visit, using the ONE claim token from their message or from the /import-statement command argument.

The token covers every file in that drop: call this tool once per token, never per file. It works once and expires an hour after the drop.

Returns one document_id per file; poll well_get_statement_import_result for each.

A refused token (expired, already claimed, unknown) is final: tell the user plainly and ask them to attach the files here, never retry. Files listed under failed were claimed but did not ingest; ask for exactly those by hand.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
claim_tokenYesThe drop's claim token, exactly as written: from the argument after /import-statement or from the user's message. Single-use, covers every statement in that drop, expires one hour after the drop.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
failedYesFiles that were claimed but did not ingest. Their bytes are gone; ask the user for exactly these by name.
drop_idNoThe drop this token belonged to. Safe to quote; the token is not.
successYes
documentsYesOne entry per file that reached the import pipeline.
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
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. Changed4 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
+  "description": "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.",
+  "type": "string"
+}
    • addedOutput schema / properties / conversation_id
      Added value: +{
+  "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"
+}
    • addedOutput schema / properties / conversation_id_note
      Added value: +{
+  "description": "Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.",
+  "type": "string"
+}
    • addedOutput schema / properties / conversation_id_source
      Added value: +{
+  "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"
+}
  2. Changed9 schema fields changed
    • changedInput schema / properties / claim_token / description
      Previous value: -"The claim token from the user's message, exactly as written. Single-use, expires one hour after the drop."New value: +"The drop's claim token, exactly as written: from the argument after /import-statement or from the user's message. Single-use, covers every statement in that drop, expires one hour after the drop."
    • removedOutput schema / properties / byte_length
      Removed value: -{
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
    • removedOutput schema / properties / content_sha256
      Removed value: -{
-  "description": "SHA-256 (hex) of the payload the server received — compare against your source to verify fidelity.",
-  "type": "string"
-}
    • removedOutput schema / properties / deduplicated
      Removed value: -{
-  "description": "True when an identical document was already in the workspace — nothing was imported twice.",
-  "type": "boolean"
-}
    • removedOutput schema / properties / document_id
      Removed value: -{
-  "description": "Poll well_get_statement_import_result with this id for the import outcome.",
-  "type": "string"
-}
    • addedOutput schema / properties / documents
      Added value: +{
+  "default": [],
+  "description": "One entry per file that reached the import pipeline.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "byte_length": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "content_sha256": {
+        "type": "string"
+      },
+      "deduplicated": {
+        "description": "True when an identical document was already in the workspace, so nothing was imported twice.",
+        "type": "boolean"
+      },
+      "document_id": {
+        "description": "Poll well_get_statement_import_result with this id for the import outcome.",
+        "type": "string"
+      },
+      "draft_id": {
+        "type": "string"
+      },
+      "filename": {
+        "type": "string"
+      },
+      "ordinal": {
+        "description": "The file's 0-based index among the files Well accepted from the drop, in arrival order.",
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "draft_id",
+      "ordinal",
+      "filename",
+      "document_id",
+      "content_sha256",
+      "byte_length",
+      "deduplicated"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / drop_id
      Added value: +{
+  "description": "The drop this token belonged to. Safe to quote; the token is not.",
+  "type": "string"
+}
    • addedOutput schema / properties / failed
      Added value: +{
+  "default": [],
+  "description": "Files that were claimed but did not ingest. Their bytes are gone; ask the user for exactly these by name.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "draft_id": {
+        "type": "string"
+      },
+      "error": {
+        "type": "string"
+      },
+      "filename": {
+        "type": "string"
+      },
+      "ordinal": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "draft_id",
+      "ordinal",
+      "filename",
+      "error"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "success"
-]New value: +[
+  "success",
+  "documents",
+  "failed"
+]
  3. Added

TDQS

A5/5.0
Behavior5/5

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

Despite annotations already marking readOnlyHint=false and destructiveHint=false, the description adds substantial behavioral context: single-use token, one-hour expiration, returns per-file document IDs, refused tokens are final, and failed files need manual re-request. No contradiction with annotations.

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?

The description is information-dense with no fluff. Each sentence adds value: token usage, polling, failure handling, and parameter nuances are all covered. It is front-loaded with the core concept and structured logically.

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 a tool with four parameters, an output schema, and complex token lifecycle, the description covers every aspect an agent needs: when to call, how to handle results, failure modes, and parameter usage. Nothing critical is missing, and the output schema covers return structure.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds significant meaning: claim_token must be exactly as written, workspace_id has omission vs. requirement rules, conversation_id propagation details, and idempotency_key semantics. This far exceeds baseline.

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?

The description states a specific verb ('Claim'), resource ('every bank statement the user dropped on Well's website'), and scope ('in one visit'). It clearly distinguishes from siblings like well_upload_statement_bytes or well_get_statement_import_result, leaving no ambiguity about what the tool does.

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?

The description explicitly says to call once per token, never per file, and to poll well_get_statement_import_result for each result. It also gives clear when-not-to-use guidance (refused tokens are final, ask user to attach files, never retry), naming an alternative action and a sibling tool.

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