Skip to main content
Glama

Group supplier quotes

well_group_quotes

Put supplier quotes in one comparison group, so well_compare_quotes compares them together. It writes only inside Well and sends nothing.

Pass supplier_quote_ids (from well_compare_quotes called with no argument) and either quote_request_id to add them to an existing group, or title (the need, in the person's words) to start a new group. A quote already in another group moves to this one. At most 10 quotes per group.

Call it only after the person named the quotes to compare together. Never group quotes on your own guess from their supplier names or their text.

refusal_reason: "quote_not_found" (an id is not a quote of this workspace; missing_supplier_quote_ids names it and nothing moved), "request_not_found", "too_many_quotes", "title_or_request_required", "no_workspace", "write_failed".

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
titleNoThe need, in the person's words, for a new comparison group. Used only without quote_request_id.
descriptionNoDetails of the need, in the person's words.
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.
quote_request_idNoAn existing comparison group to add the quotes to.
supplier_quote_idsYesThe quotes to compare together, from `well_compare_quotes`.

Output Schema

NameRequiredDescriptionDefault
errorNo
createdNo
requestNo
successYes
refusal_reasonNo
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.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
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.
grouped_supplier_quote_idsNo
missing_supplier_quote_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / request / properties / description / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / request / properties / description / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • 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"
      +]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: it writes only inside Well and sends nothing external, a quote already in another group is moved (a real side effect not implied by destructiveHint=false), the 10-quote cap, and a full enumeration of refusal_reason values including missing_supplier_quote_ids on partial failure. Workspace resolution behavior (single vs multiple authorized workspaces) is also disclosed.

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?

Purpose is front-loaded in the first sentence and the paragraphs move logically from action to parameters to constraints to refusals. Slightly long, and the closing workspace/token paragraph largely restates the workspace_id schema description, which is mild redundancy.

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 8 parameters, a write annotation profile, and an output schema present, the description still covers the things structure cannot: the move-on-regroup side effect, the group size cap, the no-guessing rule, and every refusal code. Nothing an agent needs to call this 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 coverage is 100%, so the baseline is 3; the description earns above that by defining the dependency between supplier_quote_ids and 'either quote_request_id ... or title', by sourcing the ids from well_compare_quotes, and by glossing title as 'the need, in the person's words'. It does not cover description or idempotency_key, so it stops short of a 5.

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?

Opens with a specific verb+resource ('Put supplier quotes in one comparison group') and immediately names the downstream sibling well_compare_quotes as the reason it exists. An agent can distinguish it from well_compare_quotes without opening either schema.

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?

Explicitly states the precondition ('Call it only after the person named the quotes to compare together. Never group quotes on your own guess from their supplier names or their text') and explains the either/or between quote_request_id and title. It also tells the agent how to obtain the ids (calling well_compare_quotes with no argument), which routes the agent correctly.

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