Skip to main content
Glama

Search skill

well_search_skill
Read-only

Find the Well procedure (skill) for what the user asks, when no Well skill for the request is installed or loaded in this conversation.

Returns the roster of Well skills with their descriptions; pick the one whose description matches the request, then call well_get_skill with its id and follow the returned instructions exactly.

Except for one exchange rate (see the end), call this FIRST, before any other Well data tool, for a job to carry out ("go chase", "connect", "categorize before I close") and for a question about the data ("what is", "which", "how many", "show me") alike. A skill orders the reads and the answer, so a read tool called first answers without that order.

When no skill in the roster matches the request, answer it with the matching well_* read tool. Do not call it when a Well skill for this request is installed or loaded in this conversation (use that skill, and call well_get_skill only when it tells you to), or when you already hold the id of the matching skill (call well_get_skill with it). One exchange rate or one currency conversion needs no search and no skill: call well_get_fx_quote straight away.

Input Schema

NameRequiredDescriptionDefault
queryNoWhat the user wants to do, in their own terms. The whole roster is returned either way.
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
errorNo
reasonYes
skillsYes
successYes
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. 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"
      +  }
      +]
  9. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the read-only/no-destroy profile, which the description doesn't waste words repeating. Instead it discloses non-obvious behavior: the call returns the whole roster regardless of query, it gates the ordering of all downstream reads, and it chains to well_get_skill with a follow-the-instructions obligation. That is real operational context an agent cannot infer from the schema.

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-loaded with purpose, then usage, then exclusions, then the FX carve-out — a sensible order. It runs long for a search tool and the dangling '(see the end)' forward reference in the second paragraph is a small structural wart, but nearly every sentence carries decision-relevant content.

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 says the roster comes back with descriptions. Combined with the routing to well_get_skill and the explicit exceptions, an agent has everything needed to call this correctly at the right moment.

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?

With 100% schema description coverage the schema already explains every parameter, including the note that workspace_id is optional and that the whole roster is returned either way. The description adds no parameter-level detail beyond the implicit 'no search needed' cases, so baseline 3 applies.

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 first sentence states a specific verb and resource ('Find the Well procedure (skill)') and names the exact condition it serves. The follow-up distinguishes it precisely from well_get_skill ('pick the one whose description matches... then call well_get_skill with its id'), so an agent can tell the two apart 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?

Explicit when-to-use ('call this FIRST, before any other Well data tool') covering both jobs and questions, explicit when-not ('when a Well skill for this request is installed or loaded', 'when you already hold the id'), and a named fallback sibling (well_* read tools). It even carves out a concrete exception routing to well_get_fx_quote for a single currency conversion.

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