Skip to main content
Glama
Grist MCP Server
by nic01asFr

Describe Workspace

describe_workspace

Retrieve detailed information about a specific Grist workspace using its workspace ID.

Instructions

Obtient des informations détaillées sur un espace de travail spécifique.

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_id": "<workspace_id>"
    },
    "name": "describe_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesL'ID de l'espace de travail à décrire

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / workspace_id / description
      Added value: +"L'ID de l'espace de travail à décrire"
  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 supplied, so the description carries the full burden. "Obtient" implies a read-only operation, but the definition says nothing about permissions required, what "informations détaillées" actually encompasses (settings, members, metadata), or whether it errors on a missing workspace.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity comes partly from omitting information rather than from tight editing.

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?

The tool is simple (one required param) and an output schema exists, so return values need not be explained. Still, with no annotations and no statement of scope or permissions, the definition is only minimally adequate for an agent to invoke it confidently.

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?

There is a single required parameter and schema description coverage is 100%, with the schema already labeling workspace_id as "L'ID de l'espace de travail à décrire". The description adds no format, source, or lookup guidance beyond that, so the baseline of 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?

"Obtient des informations détaillées sur un espace de travail spécifique" states a clear verb (obtain/read) and a specific resource (workspace), so an agent can tell it targets workspaces rather than documents or organizations. It does not, however, explicitly differentiate itself from the sibling describe_document / describe_organization beyond the noun.

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 offers no when-to-use guidance, no prerequisites (e.g. needing a valid workspace_id or permission), and no mention of alternatives such as list_workspace_access or modify_workspace. Usage is only inferable from the verb.

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