Skip to main content
Glama

List workspaces

ricursor_workspaces
Read-only

The workspace this key can reach.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ricursor_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, so the safety profile is covered. The description does contribute one genuinely useful behavioral fact beyond annotations: results are limited to what the supplied key can reach, which is auth scoping. It says nothing about return shape (single workspace vs. list) or any rate limits, so it earns only partial credit.

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?

Extremely short with no padding, so nothing is wasted. However, the single clause is a fragment rather than a front-loaded statement of action and scope, so brevity here reflects under-specification more than disciplined writing.

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?

The tool is simple - no parameters, no output schema - so a one-liner could suffice, but this one omits the action verb and does not clarify whether the result is a single workspace or a collection, contradicting the plural in the title. An agent can guess its purpose but not describe its return confidently.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics for the description to add. The mention of "this key" is consistent with a credential-derived call rather than an argument, which is correct but not extra detail.

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

Purpose2/5

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

The description is a noun fragment, "The workspace this key can reach," with no verb stating what the tool actually does. Only the title ("List workspaces") supplies the action, and the fragment is singular while the title is plural, leaving the agent to reconcile the two. It adds a scope notion (key-reachable workspace) but never states the operation.

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?

There is no when-to-use guidance at all - no mention of alternatives among the many ricursor_* siblings, no prerequisites, no exclusions. An agent must infer from names alone that this is a context/bootstrap call rather than an action or check tool.

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