AlphaWeb

connections_list

Read-only

Connection ids/status/app actions/tracking/requests; catalog mode finds connectable apps.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>"
    },
    "name": "connections_list"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No
`limit`	No
`query`	No
`cursor`	No
`request`	No
`category`	No
`workspace`	Yes
`app_category`	No
`include_requests`	No
`include_tracking`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds that results can include ids/status/app actions/tracking/requests and that catalog mode finds connectable apps, but it omits pagination behavior from limit/cursor, filtering behavior, and output structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is brief, but the semicolon-separated phrase is cryptic rather than front-loaded and reads like keyword stuffing. It avoids waste but at the cost of clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter, read-only listing tool with no output schema, the definition is not complete enough: pagination, filtering, and return structure are undocumented. Annotations cover safety but do not substitute for operational guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are 10 parameters with 0% schema description coverage. The description gives only implicit semantics for mode and some entity fields (tracking/requests), leaving limit, cursor, query, category, app_category, workspace, and the enum/filter behavior unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (connections) and enumerates returned aspects (ids/status/app actions/tracking/requests) plus a catalog mode, but it omits a clear verb such as 'list' and reads as a fragment. It does not explicitly differentiate from siblings like connections_actions or connections_connect, though the catalog mode phrase is somewhat distinctive.

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

Usage Guidelines2/5

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

Only implied guidance is present: 'catalog mode finds connectable apps.' It does not say when to choose this tool over connections_actions, connections_connect, or catalog_list, nor when connected versus catalog mode is appropriate beyond that brief phrase.

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

All AlphaWeb 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?