Skip to main content
Glama

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, or the one claim link from Well's website that carries it (https://wellapp.ai/find-missing-invoices/#claim=...). Pass the link exactly as given; the tool reads the token out of it.

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

NameRequiredDescriptionDefault
claim_tokenYesThe drop's claim token, or the claim link from Well's website that carries it, 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.
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.

Output 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.
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.
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 / newly_connected / description
      Previous value: -"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. Start the reply with 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."New value: +"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."
  2. Changed1 schema field changed
    • addedInput schema / properties / workspace_scope
      Added 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"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / newly_connected
      Added value: +{
      +  "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. Start the reply with 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"
      +}
  4. Changed2 schema fields changed
    • changedInput schema / properties / claim_token / description
      Previous 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."New value: +"The drop's claim token, or the claim link from Well's website that carries it, 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."
    • removedInput schema / properties / claim_token / pattern
      Removed value: -"^[A-Za-z0-9_-]{43}$"
  5. 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"
      +}
  6. 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"
      +]
  7. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover readOnly/destructive/openWorld; the description adds the high-value operational facts an agent cannot infer: single-use token, one-hour expiry from the drop, refusal states are terminal (expired/already claimed/unknown), and that 'failed' files were claimed but did not ingest. This directly shapes recovery behavior.

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-loads the core action and the too-many-calls-per-file warning immediately, then sequences follow-up, expiry, and failure handling. Dense with actionable content, though the multi-paragraph form is longer than strictly necessary for a single-claim tool.

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?

With an output schema present and five parameters, the description still covers the return contract (one document_id per file, poll each), the token lifetime, and terminal-failure handling. Nothing needed to invoke or recover correctly is missing.

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 description coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema: it tells the agent the link can be passed verbatim because the tool extracts the token, and it explains the omit-vs-require logic for workspace_id when the token authorizes multiple workspaces.

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+resource+scope: claiming every bank statement the user dropped on Well's website via one claim token. It also implicitly distinguishes itself from well_get_statement_import_result, which it names as the follow-up poll target, and from the upload tools by requiring a token rather than file bytes.

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?

Explicit about when to call (once per token, never per file), what to pass (the token or link 'exactly as given'), what to do after (poll well_get_statement_import_result per document_id), and what never to do (never retry a refused token; ask for failed files by hand). This is a full call protocol, not just a context hint.

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