Skip to main content
Glama

get_workspace_health

Read-onlyIdempotent

Current workspace adoption health: score (0-100), band (healthy | watch | at_risk), and trailing 30-day signals. health is null until the daily rollup has run. Use when checking whether the workspace is actively using automations.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the read-only and idempotent annotations, it discloses the trailing 30-day window and the important availability behavior that health is null until the daily rollup has run. It does not further explain snapshot freshness or what the individual signals contain, but the rollup dependency is especially useful operational context.

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?

Three short sentences front-load the returned health information, then state the null/rollup caveat and the intended use case. Every sentence adds actionable information without filler or repetition of the annotations.

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-argument read with no output schema, it covers scope, score range, band values, time window, availability behavior, and intended question. Enumerating the trailing signals or clarifying rollup freshness would improve completeness, but those omissions do not impede correct invocation.

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?

There are no parameters, so the empty input schema is sufficient and the zero-parameter baseline applies. The phrase "Current workspace" usefully confirms the implicit scope and avoids any expectation that a workspace identifier must be supplied.

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 clearly identifies the resource as current workspace adoption health and specifies its score, band, and trailing signals. The automation-adoption use case gives it a distinct purpose, but it does not explicitly differentiate itself from related workspace reporting siblings.

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?

It gives a concrete selection condition: "Use when checking whether the workspace is actively using automations." This provides clear context, though there is no when-not guidance or explicit alternative for adjacent questions such as trends or returns.

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