Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Get workspace info

get_workspace_info
Read-only

Retrieve current workspace details—name, slug, organization plan, and pooled plan limits—to check available resources and quotas.

Instructions

Get the current workspace's info: name, slug, its organization's plan and the plan limits pooled across the organization - workspaces, member seats, pages, storage, upload size, Content API requests and transfer per month, orders per month, and whether single sign-on is included. Only pages and orders can be unlimited (null).

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.73.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful value on top by enumerating what is returned and warning that only pages and orders can be unlimited (null), which prevents misreading nulls. It adds no permission or error-case context, but for a safe read that is a minor gap.

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 that leads with the verb and resource, then lists returned fields. The enumeration is long but functional given there is no output schema; a slightly tighter grouping of the plan-limit items would improve it.

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

Completeness4/5

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

With no output schema, the description must carry the return-value burden, and it does so by naming the returned fields and the null semantics for unlimited values. It does not clarify the shape of the returned data (flat vs. nested plan-limits object), which leaves a small ambiguity for an agent consuming the result.

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 tool takes zero parameters, so there is nothing for the description to disambiguate beyond what is implied, and the definition correctly implies no arguments by scoping to the "current" workspace. Baseline 4 applies for a parameterless tool.

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 gives a specific verb and resource ("Get the current workspace's info") and enumerates the contents: name, slug, organization plan, and plan limits. It does not explicitly contrast itself with any sibling such as get_site_config or get_customer, so it stops short of a 5.

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?

Usage is only implied: an agent can infer this is the tool to call when it needs organization-level plan and limit data. There is no explicit when-to-use statement, no exclusions, and no named alternative (e.g., when to prefer get_site_config or get_customer).

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

Deploy Server

Other Tools