Skip to main content
Glama
Grist MCP Server
by nic01asFr

List Workspaces

list_workspaces

Lists all workspaces in a Grist organization by organization ID, helping you discover workspace IDs for document and data management tasks.

Instructions

Liste tous les espaces de travail dans une organisation Grist.

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": {
      "org_id": "<org_id>"
    },
    "name": "list_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_idYesL'ID de l'organisation (entier ou sous-domaine string)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / org_id / description
      Added value: +"L'ID de l'organisation (entier ou sous-domaine string)"
  2. First observedv0.1.0

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 behavioral burden, yet it discloses nothing beyond the resource being listed. It does not say whether results are paginated, whether the caller needs org-level access, whether inactive workspaces are included, or whether listing is exhaustive — all material for a read tool with no safety hints.

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?

One short, front-loaded sentence with no wasted words. It is efficient, though it is also shorter than the tool's behavioral gaps warrant, and the description language differs from the English title.

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?

An output schema exists and the sole parameter is fully documented, so the description needn't explain return values. However, for a tool with no annotations, the omission of access requirements, result scope, and usage routing leaves it only minimally complete.

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%: the single org_id parameter is fully documented in the schema, including that it accepts an integer ID or a string subdomain. The description adds no meaning beyond that, so the baseline 3 applies.

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 ('Liste tous les espaces de travail') and adds scope ('dans une organisation Grist'), so an agent knows it returns workspaces filtered by organization. It does not explicitly contrast with neighbors like list_organizations or describe_workspace, but the resource noun is unambiguous.

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, no mention of alternatives such as describe_workspace (for a single workspace) or list_documents (for contents), and no prerequisites or exclusions. The agent must infer from the name alone that this is the enumeration step before further per-workspace calls.

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