AlphaWeb

skills_list

Read-only

Read built-in and custom skills with connection readiness. Custom instructions on request.

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": "skills_list"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`skill`	No
`cursor`	No
`module`	No
`source`	No
`category`	No
`workspace`	Yes
`include_instructions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

C2.9/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, non-destructive operation. The description adds some useful context by mentioning "connection readiness" and that custom instructions are available "on request," but it does not explain pagination behavior or other operational details.

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?

The description is short and front-loaded, using only two sentences with no obvious bloat. However, "connection readiness" is somewhat cryptic and could be clearer without adding much length.

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 9-parameter listing tool with no output schema and no parameter descriptions, the description is too sparse. It omits the required workspace parameter, filtering options, pagination behavior, and what the returned skill entries or connection readiness contain.

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?

Schema description coverage is 0% across 9 parameters, so the description must carry the burden. It only loosely maps "built-in and custom" to the source parameter and "custom instructions on request" to include_instructions, leaving workspace, query, skill, module, limit, cursor, and category unexplained.

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?

The description states a specific verb and resource: "Read" skills, with scope limited to built-in and custom skills. It is fairly clear that this is a listing/read tool, but it does not explicitly distinguish itself from the sibling skills_save tool.

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?

The description does not state when to use this tool versus alternatives such as skills_save, nor does it include exclusions or prerequisites. Usage is only implied by "Read built-in and custom skills."

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?