Skip to main content
Glama

Workspace info

workspace_info
Read-onlyIdempotent

Start here. Returns who this key belongs to: workspace name, plan, the scopes this key has, and the brand (voice, colors, from name, sending domain). Free and read only; uses no quota. Call it at the start of a conversation so you know which tools this key may use and how to write on-brand. Requires API key scope: read.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds information not present in structured fields: it is free, consumes no quota, and requires the 'read' API key scope. It does not describe response shape in detail (e.g. field types for the nested brand data) or failure behavior when the key lacks scope.

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?

Front-loaded with the imperative 'Start here', then payload, then cost/auth constraints — a sensible ordering that lets an agent decide quickly. Minor redundancy between 'Free and read only' and the readOnly annotation, but 'uses no quota' earns its place.

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?

For a zero-parameter read tool with no output schema, the description is nearly complete: it names the returned fields, the cost profile, and the auth scope. Only the internal structure of the brand object and error conditions for insufficient scope are left implicit.

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; baseline 4 applies. The schema is empty and fully self-consistent with the no-argument call described.

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 ('Returns') with an enumerated payload: workspace name, plan, key scopes, and brand details (voice, colors, from name, sending domain). This distinguishes it from siblings like account_get and brand_get without needing to open their schemas.

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

Usage Guidelines4/5

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

'Start here' plus 'Call it at the start of a conversation so you know which tools this key may use and how to write on-brand' gives explicit when-to-use guidance and a stated purpose for the call. It does not explicitly exclude or name alternatives such as brand_get for brand fields, so it stops short of full routing guidance.

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.

Resources