teamgrid_workspace_get is a read-only TeamGrid MCP tool. It is advertised in: all, collaboration, context, core, governance, work, full, schedule-write, content-write, admin-write, automation-write, crm-write, catalog-write, integrations-write, projects-write, finance-write, tasks-write, time-write.
Get the authenticated workspace
Arguments at a glance
The table describes full. When a profile variant is shown below, use that variant’s exact schema.
| Argument | Presence | Type | Meaning |
|---|---|---|---|
| — | — | — | Use an empty object: {}. |
Input schema
Stable release: this is the exact JSON Schema advertised by @teamgrid/mcp-server@1.2.2:
{
"type": "object",
"properties": {},
"required": [],
"additionalProperties": false
}The schema above is for full. Properties not in the selected profile schema are rejected.
Input in all
{
"type": "object",
"properties": {},
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false
}Input in collaboration
{
"type": "object",
"properties": {},
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false
}Input in core
{
"type": "object",
"properties": {},
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false
}Input in governance
{
"type": "object",
"properties": {},
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false
}Scope and API operation
Required scopes (all): workspace:read.
getWorkspace—GET /workspace
The credential must also satisfy normal workspace authorization and any service-account resource grants. Selecting an MCP tool profile never adds scopes to a credential.
Read behavior
This tool does not change business state.
Output and limits
The bounded API result is returned as MCP structured content and equivalent JSON text. This tool returns a single API response envelope and is not paginated. The serialized result may not exceed 256 KiB.
Download the exact MCP input and output contract, including profile variants, scopes and safety annotations. Its outputSchema describes the advertised MCP envelope and local $defs; it includes MCP projection metadata in addition to the underlying API schema.
The linked API operation describes the business resource and its field semantics. Write tools preserve their declared revision/idempotency contract and require current permissions. Accepted jobs provide status/resume information; uncertain writes must not be replayed blindly.
Security classification
tenant-metadata: The response identifies the authenticated workspace, region, and cell.
The exact safety annotations are {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}. The host and model can still retain tool
arguments and results in prompts, logs, or transcripts; use a dedicated least-privilege credential.
Example prompt
Use TeamGrid to show the authenticated workspace and its region. Do not call any write-capable tool.
The prompt is illustrative. Inspect the proposed tool arguments before approving access to personal, commercial, conversation, or security-configuration data.
Common failures
| Condition | Observable behavior and recovery |
|---|---|
| An argument violates this tool’s input schema: required field, type, enum, pattern, length, or range. | MCP input validation rejects the call before an API request is made. |
The credential lacks workspace:read or cannot access the requested resource. |
The tool preserves a safe API error code such as insufficient_scope, with redacted detail and available status/request metadata. |
| A read exceeds the 256 KiB tool result limit. | Use a bounded section, smaller supported read, private resource or authorized App/CLI transfer. |
| An unknown input property is supplied. | The strict input schema rejects the call before an API request is made. |
Authentication failures that prevent the MCP process from starting are covered separately in MCP troubleshooting.