Skip to main content
Glama

Get skill

well_get_skill
Read-only

Get the Well procedure for a job, written by the Well team, and follow it exactly: ONE markdown document, the instructions for the thing you are about to do. Its content is the instruction, not background reading: do what it says, in the order it says, and do not substitute your own plan for it.

A document may tell you to run other Well skills: load each one with this tool, by the id the document names, at the moment the document says to. Use well_search_skill first when you do not already hold the id; the catalog is fixed for the life of the server, so re-fetching a document you already hold buys nothing.

Input Schema

NameRequiredDescriptionDefault
realNoLoad exactly this slug, with no demo-variant swap, even in a demo workspace. Set this only when a skill's own workflow reaches a sibling skill by name mid-step — a board's own feed load, for instance — where the exact slug is already decided and must not be substituted.
skillYesThe id of the skill to load, as well_search_skill lists it.
workspace_idNoTarget workspace. Optional: this tool describes the token itself rather than one workspace's data, so omitting it returns the same answer.
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.
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
bytesYes
errorNo
skillYes
reasonYes
successYes
documentYes
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 / reason / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "skill_unknown",
      -      "catalog_unreadable",
      -      "write_skill_in_app",
      -      "closing_held_by_earlier_turn",
      -      "closing_after_named_tool_not_in_well",
      -      "closing_after_tool_capability"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "skill_unknown",
      +      "catalog_unreadable",
      +      "write_skill_in_app",
      +      "closing_held_by_earlier_turn",
      +      "closing_after_named_tool_not_in_well",
      +      "closing_after_tool_capability",
      +      "unsupported_host"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / reason / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "skill_unknown",
      -      "catalog_unreadable",
      -      "write_skill_in_app",
      -      "closing_held_by_earlier_turn",
      -      "closing_after_named_tool_not_in_well"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "skill_unknown",
      +      "catalog_unreadable",
      +      "write_skill_in_app",
      +      "closing_held_by_earlier_turn",
      +      "closing_after_named_tool_not_in_well",
      +      "closing_after_tool_capability"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Changed1 schema field changed
    • changedOutput schema / properties / reason / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "skill_unknown",
      -      "catalog_unreadable",
      -      "write_skill_in_app",
      -      "closing_held_by_earlier_turn"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "skill_unknown",
      +      "catalog_unreadable",
      +      "write_skill_in_app",
      +      "closing_held_by_earlier_turn",
      +      "closing_after_named_tool_not_in_well"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  4. Changed1 schema field changed
    • changedOutput schema / properties / reason / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "skill_unknown",
      -      "catalog_unreadable",
      -      "write_skill_in_app"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "skill_unknown",
      +      "catalog_unreadable",
      +      "write_skill_in_app",
      +      "closing_held_by_earlier_turn"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  5. 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."
  6. 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"
      +}
  7. 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"
      +}
  8. Changed1 schema field changed
    • addedInput schema / properties / real
      Added value: +{
      +  "description": "Load exactly this slug, with no demo-variant swap, even in a demo workspace. Set this only when a skill's own workflow reaches a sibling skill by name mid-step — a board's own feed load, for instance — where the exact slug is already decided and must not be substituted.",
      +  "type": "boolean"
      +}
  9. Changed5 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"
      +}
    • changedOutput schema / properties / reason / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "skill_unknown",
      -      "catalog_unreadable"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "skill_unknown",
      +      "catalog_unreadable",
      +      "write_skill_in_app"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  10. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description goes beyond them with genuinely non-obvious behavior: the return value is an imperative instruction to be executed in order rather than background reading, and documents can chain into further skill loads. It stops short of describing format/length or failure behavior when an id is unknown, so it is strong but not exhaustive.

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?

It is front-loaded with the core meaning and the second paragraph handles chaining and caching efficiently. There is mild redundancy between 'follow it exactly' and 'do what it says, in the order it says, and do not substitute your own plan for it', which restates the same mandate twice for emphasis.

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, so return values need no explanation, and the description covers the remaining agent-critical questions: what the document is, how binding it is, how nested skills are loaded, and when re-fetching is pointless. Nothing needed to invoke it 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 five parameters — including the subtle 'real' flag and the conversation_id/workspace_scope plumbing — are already documented in the schema. The description only reinforces the 'skill' parameter by tying ids to well_search_skill output; it says nothing about 'real', 'workspace_id' or 'workspace_scope'. Baseline 3 is appropriate when the schema carries the parameter burden.

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 and resource — get the Well procedure/skill document for a job by id — and characterizes the payload precisely ('ONE markdown document, the instructions for the thing you are about to do'). It is clearly distinguishable from the sibling well_search_skill, which is named as the lookup path rather than the loader.

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?

It gives explicit routing: use well_search_skill first when you do not already hold the id, load each nested skill with this tool at the moment the document says to, and do not re-fetch a document you already hold because the catalog is fixed. That covers when to use, when not to, and the alternative.

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