Well

Check a custom server address

well_probe_mcp_server

Read-onlyIdempotent

Check the address of an MCP server that a person gave for a tool Well's catalog does not carry, before anyone connects it. It sends a few read-only requests to a public https address (the MCP "initialize" request and the OAuth discovery documents), follows no redirect to a private or non-https address, and names the sign-in the server asks for. It writes nothing, signs in to nothing and sends no credential.

Call it only with an address the person gave, after a well_list_connectors read with the tool's slug (then q) found no connectable row. Read outcome:

"mcp_server": name the sign-in in words from sign_in (no sign-in, a key to paste, or a sign-in on the tool's own page).
"not_mcp_server": say the address answers but is not an MCP server, and ask once for the server's address (often a path such as /mcp or /sse).
"unreachable": say the address did not answer, and ask the person to check it.
"address_refused": say Well connects only to a public https address. Nothing was sent.

Never write the full address back in a log line or a public place.

Input Schema

Name	Required	Description
`url`	Yes	The full address of the MCP server, exactly as the person gave it, e.g. "https://mcp.example.com/mcp". Never an address you composed or guessed.
`workspace_id`	No	Target workspace. Optional: this tool describes the token itself rather than one workspace's data, so omitting it returns the same answer.
`conversation_id`	No	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.
`workspace_scope`	No	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.

Output Schema

Name	Required	Description
`host`	No	The host of the address, to name the server in your line.
`error`	No
`outcome`	No	"mcp_server" (the address answers as an MCP server), "not_mcp_server" (it answers, but not as an MCP server), "unreachable" (no answer in time), or "address_refused" (not a public https address; nothing was sent).
`sign_in`	No	Only for "mcp_server": "none" (no sign-in), "api_key" (a key or token the person pastes), "oauth" (the person signs in on the tool's own page), or "unknown" (the check did not finish). Null for every other outcome.
`success`	Yes
`conversation_id`	No	The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
`newly_connected`	No	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.
`conversation_id_note`	No	Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.
`conversation_id_source`	No	Where 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.

Changed2 schema fields changedOct 28, 2026
- removedOutput schema / properties / host / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / host / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedOct 12, 2026

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."

Changed1 schema field changedOct 8, 2026

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"
+}

Changed1 schema field changedOct 6, 2026

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"
+}

AddedOct 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations: it names what is actually sent (the MCP initialize request and OAuth discovery documents), the SSRF guard (no redirect to private or non-https), and what it will not do (writes nothing, signs in to nothing, sends no credential). It also adds a confidentiality constraint about not echoing the full address.

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 the action and safety posture, then a precondition, then a well-structured outcome table. Slightly long and the outcome bullets repeat wording that also appears in the output schema, but every line carries actionable guidance for the agent.

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?

For a one-shot probe against an external address with an output schema present, the description covers the trigger condition, the network behavior, the safety boundaries, and how to interpret each outcome. Nothing an agent needs in order to call it 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 adds a genuine constraint beyond the schema by requiring the url be exactly as the person gave it and warning against a composed address (the schema says this too, but the description reinforces it as a hard rule). The other three parameters (workspace_id, conversation_id, workspace_scope) are not discussed, but they are fully documented in the schema.

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 (check), resource (the address of an MCP server the catalog does not carry) and scope (before anyone connects it), which is immediately distinguishable from well_add_custom_connector and well_list_connectors. An agent knows exactly what action this performs without opening the 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?

Gives an explicit gate: only call with an address the person gave, and only after well_list_connectors with the tool's slug (then q) found no connectable row. It also routes each outcome value to a next conversational action, so when-to-use and what-to-do-next are both covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Well tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?