Skip to main content
Glama

Create agent seat

well_create_agent_seat

Add an agent to the current workspace: a seat a workspace agent holds, with a name, the line that says what it handles, and a sponsor (the member who answers for it and reads its reports).

Use this tool when an owner or an admin asks to add an agent ("Add an agent that chases late invoices"). The complete order is the yes: the agent is saved at once.

REQUIRED: name. OPTIONAL: duty (what the agent handles, in the person's words), sponsor_membership_id (a member who is a person; defaults to the person who asks).

An agent holds the member role only, never the invoice right, and never signs in. It is never an owner, an admin or a person. Only an owner or an admin adds one. Two agents of one workspace never share a name.

Returns { success: true, seat_id, name, duty, sponsor } or { success: false, error }.

Input Schema

NameRequiredDescriptionDefault
dutyNoWhat the agent handles, in the person's words, such as "customer reminders".
nameYesThe agent's name, as the person gives it. When the person gives none, use a name that says the job, such as "Late invoices".
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.
sponsor_membership_idNoThe membership id of the member who answers for the agent. Omit it: the person who asks is the sponsor.

Output Schema

NameRequiredDescriptionDefault
codeNo
dutyNo
nameNo
errorNo
seat_idNo
sponsorNo
successYes
reply_linesNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
near_candidatesNo
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.
near_candidates_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedOutput schema / properties / code
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / duty / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / duty / 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"
      +}
    • removedOutput schema / properties / sponsor / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / sponsor / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / sponsor / properties / person_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / sponsor / properties / person_id / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"The agent's name, such as Hélène."New value: +"The agent's name, as the person gives it. When the person gives none, use a name that says the job, such as \"Late invoices\"."
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations it discloses substantive behavior: the create is immediate ('the agent is saved at once'), the resulting seat is a member-role-only identity that never holds invoice rights, never signs in, and can never be owner/admin/person. It also surfaces a uniqueness constraint ('two agents of one workspace never share a name') and the exact success/error return shape, which is exactly the kind of side-effect detail an agent needs before writing.

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?

Well front-loaded: purpose first, then the trigger condition, then parameter summary, then constraints, then return shape. A few sentences are ornamental ('the complete order is the yes', 'the line that says what it handles') and could be trimmed, but the information density is high and the ordering matches how an agent reads a definition.

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?

An output schema exists and the description still summarizes the return contract compactly, and it covers the permission requirement, the name-uniqueness rule, identity constraints, and defaulting behavior for the sponsor. Combined with 100% schema coverage on the remaining operational parameters, nothing an agent needs to invoke this correctly is missing.

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 description coverage is 100%, so all seven parameters — including workspace_id, conversation_id, idempotency_key and workspace_scope — are already documented in the schema. The description's 'REQUIRED: name / OPTIONAL: duty, sponsor_membership_id' block mostly restates that, though it usefully reiterates that sponsor defaults to the requesting person. Baseline 3 applies since the schema carries the weight.

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 — 'Add an agent to the current workspace' — and then defines the seat object concretely (name, duty, sponsor). An agent can distinguish this from well_update_agent_seat or well_delete_agent_seat by the 'Add'/'saved at once' framing, but the description never names those siblings explicitly, leaving that inference to the verb alone.

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

Usage Guidelines4/5

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

Gives a clear trigger ('Use this tool when an owner or an admin asks to add an agent') with a realistic example utterance, plus the permission gate ('Only an owner or an admin adds one'). It does not state when to prefer an alternative tool (e.g., update vs. create, or hand-off to well_list_agent_seats to check name collisions), so it falls short of full routing guidance.

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