Skip to main content
Glama

Get the current workspace

get_workspace
Read-onlyIdempotent

Use this when you need to know whose workspace this connection acts on and what it may do: the workspace name, plan tier and size (the contacts the plan holds), how it is billed, how many contacts count toward the limit right now, and the scopes the connection holds. Also use it when the founder asks about their plan, its limits or what it includes. Not for audience numbers in a report (use get_audience_stats) or for the projects (use list_projects). complimentary is true for a plan given rather than sold.

It also tells you the plan up front, read from the plan registry: limits (contact size, campaign emails a month, projects), usage against them (including hidden_contacts, saved contacts held past the size), and includes (whether the plan sends broadcasts, runs automations, saves custom segments, shows where signups came from, lists the page in search engines and removes the badge). Use it to mention a limit before the founder hits it, never to guess one. upgrade_url opens this workspace's plan page. When contacts are held there is also an upgrade object with the plan that holds them. Give the link when the founder asks about plans or something is blocked, and say which plan removes it and why it matters for what they asked. Never quote a price or a limit that this result does not state.

key.mode says how you are connected. agent means a signed-in person approved this app (OAuth, as in ChatGPT and Claude), so "me" is that person and tools that default to them (like send_test_broadcast) work without asking for an address. Any other mode is an API key with nobody behind it. key.project tells you whether the key is pinned to a single project, in which case every other tool can only reach that one.

usage.contacts is the BILLABLE count, which excludes test-mode and flagged contacts, so do not use it to report how many signups there are.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, but the description adds substantial context beyond them: `key.mode` determines whether a signed-in person is behind the connection, `key.project` can pin the key to one project, and `usage.contacts` is billable rather than signup count. It also explains `upgrade_url`, `upgrade`, `limits`, `usage`, and `includes` in practical terms, and warns against quoting unsupported prices or limits.

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 long but front-loads the primary use case and exclusions before unpacking the result fields. Every paragraph serves a clear purpose: routing, plan details, upgrade guidance, connection mode, and usage caveats, with no redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must carry return-value meaning, and it does: `limits`, `usage`, `includes`, `upgrade_url`, `upgrade`, `key.mode`, and `key.project` are all explained. It also covers important behavioral caveats such as billable contacts excluding test-mode and flagged contacts.

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?

With zero parameters, there is no input schema to clarify and the baseline is 4. The description does not need parameter semantics here; its effort goes into output field meaning instead, which is appropriate.

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?

States a specific verb and resource: get the current workspace, including whose workspace it is, plan tier, size, billing, contact count, and scopes. It explicitly distinguishes itself from `get_audience_stats` and `list_projects`, so an agent can choose correctly without opening another schema.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance, including founder questions about plans, limits, and blocked features. It also gives clear exclusions: not for audience numbers in a report (use `get_audience_stats`) or projects (use `list_projects`).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.