google-workspace-mcp

meet_get_space

Retrieve Google Meet meeting space details by its resource name, such as 'spaces/abc-defg-hij'.

Instructions

Get details about a Google Meet meeting space by its resource name (e.g. 'spaces/abc-defg-hij').

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": {
      "space_name": "<space_name>"
    },
    "name": "meet_get_space"
  }
}

Input Schema

Name	Required	Description	Default
`space_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, and the description only says 'Get details'. It does not disclose whether this is read-only, what permissions are required, or any potential error behaviors. The description leaves the safety and side-effect profile entirely implicit.

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?

The description is a single concise sentence that includes a clarifying example. It is front-loaded with the action and resource, with no unnecessary words.

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 with one parameter and has an output schema, so return values are adequately covered. However, the absence of usage guidance and behavioral transparency means the description is only minimally complete for an agent to correctly select and invoke the tool.

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 schema only provides the parameter name and type. The description adds valuable meaning by explaining the expected format and giving a concrete example ('spaces/abc-defg-hij'), which compensates for the 0% schema description coverage.

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

Purpose5/5

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

The description uses a specific verb ('Get') with a clear resource ('Google Meet meeting space') and provides an example resource name. It unambiguously distinguishes this from sibling tools like meet_create_space or meet_list_conference_records.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have a resource name and need details, but it does not explicitly state when to use this tool versus alternatives (e.g., listing conference records). No exclusions or alternative tool references are provided.

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

Deploy Server