Skip to main content
Glama

get_user_status

Retrieve do-not-disturb state and custom status for user IDs from list_members; users without status, such as bots, are returned under no_status.

Instructions

Do-not-disturb state and custom status of users (ids from list_members).

Users Google returns no status for (e.g. bots) are listed under no_status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_ids": "<user_ids>"
    },
    "name": "get_user_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it discloses one genuinely useful edge case — users Google returns no status for (e.g. bots) appear under no_status — which prevents an agent from misreading a missing entry as an error. It says nothing about permissions, auth, batch-size limits, or whether the call is read-only, leaving the safety profile implicit in the 'get' verb.

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?

Two short sentences, front-loaded with the returned data and then the edge case — nothing extraneous. The trailing parenthetical in the first sentence is slightly awkward but costs almost nothing.

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?

An output schema exists, so return shape is already covered, and the description still adds the no_status grouping that schema alone may not make obvious. For a one-parameter read tool this is close to sufficient; only input batching and failure behavior for unknown ids remain unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% on the single user_ids parameter, so the description must compensate; it partially does by pointing to 'ids from list_members' as the source. It does not clarify that the parameter is an array, whether a single string is accepted, any maximum batch size, or whether unknown ids error or fall into no_status.

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 names a specific resource ('do-not-disturb state and custom status of users'), which is clearly narrower than the sibling list/search tools. It omits an explicit verb, but 'get_user_status' plus the field list leaves no ambiguity about what is returned. It is clear without being explicitly contrasted against an alternative.

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?

It tells the agent where to obtain inputs ('ids from list_members'), which implies the natural call sequence, but there is no explicit statement of when to use this versus fetching a full member profile or other sibling tools. Usage is implied rather than stated.

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