Skip to main content
Glama
@elido/mcp-server

@elido/mcp-server

Official
by elidoapp

list_workspaces

Enumerate the workspaces available to your API key so you can identify and select the correct workspace for managing short links, QR codes, and click analytics.

Instructions

Enumerate workspaces this API key has access to.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/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 behavioral burden and it does not disclose result shape, ordering, pagination, or whether archived/inaccessible workspaces are excluded. Only the auth scoping ("this API key") is conveyed.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler; the resource and scope come first and nothing redundant is added.

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?

For a zero-argument list tool with no output schema and no annotations, the description omits what a returned workspace contains and whether the list is paginated or exhaustive. It is minimally sufficient to select the tool but not to interpret its result.

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 there is nothing the description needs to explain; baseline 4 applies. No meaning is lost or contradicted.

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?

Specific verb ("Enumerate") plus specific resource ("workspaces") and a clear scope qualifier ("this API key has access to"). It does not name alternatives, but the sibling set (links, QR, analytics) is so distinct that no disambiguation is needed in practice.

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 explicit when-to-use or when-not-to-use guidance; the description only states what the tool returns. For a discovery/enumeration tool an agent must infer that this is the first step before any workspace-scoped call, which the text never says.

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