keyshade-mcp

Official

by keyshade-xyz

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

list_workspace_roles

Retrieve all roles within a workspace. Requires workspace slug; supports pagination, sorting, filtering, and search.

Instructions

Lists all roles within a specific workspace

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": {
      "workspaceSlug": "<workspaceSlug>"
    },
    "name": "list_workspace_roles"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (0-based)
`sort`	No	Sort field
`limit`	No	Number of items per page
`order`	No	Sort order
`search`	No	Search query
`workspaceSlug`	Yes	The slug of the workspace

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It fails to mention behavioral traits like pagination (implied by param schema), rate limits, or authentication requirements. The tool returns a list, but no further 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 a single, efficient sentence. It is front-loaded with the core purpose, though it could incorporate parameter hints without losing conciseness.

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

Completeness3/5

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

Given no output schema, the description does not explain return values. With 6 parameters and full schema coverage, the description provides minimal additional completeness. Behavioral aspects are 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 the schema already documents all 6 parameters. The tool description does not add any additional context or usage details beyond the schema, resulting in a baseline score.

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 clearly states the verb 'lists' and the resource 'roles within a specific workspace'. It distinguishes from siblings like 'list_workspace_members' but could be more specific about what constitutes a role.

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?

No guidance on when to use this tool versus alternatives (e.g., 'get_workspace_role' for a single role) or any prerequisites. The description lacks explicit context for usage.

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