Skip to main content
Glama
Sign In
infralayers

pumble-mcp

Official
by infralayers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_my_custom_status

Set or clear the authenticated user's Pumble custom status with emoji, status text, and expiration options.

Instructions

Update the custom status of the authenticated user.

Input Schema

NameRequiredDescriptionDefault
codeNoEmoji code shorthand (e.g. ':joy:'). Send empty string or omit to clear.
statusNoThe status message text (max 128 chars). Send empty string or omit to clear.
expiresAtNoThe exact timestamp when the status expires. Required only if expiration is 'custom'.
expirationNoStatus expiration mode (e.g., 'never', 'min30', 'thisWeek'). Defaults to 'never'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it omits that this is a mutation, whether omitted fields are cleared or left untouched, permission requirements, and rate limits. The subtle clear-via-empty-string semantics exist only in the schema, not the description.

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 with zero filler. It is efficient, though its brevity borders on under-specification for a four-parameter mutation.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description should disclose replace-vs-merge semantics, clearing behavior, and the response shape. None of that is present, leaving the agent dependent entirely on the input schema.

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 description coverage is 100% and each of the four parameters is documented inline, including the expiration enum and the custom-expiresAt dependency. The description adds nothing beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ("Update the custom status") and scopes it to "the authenticated user," making it unambiguous which record is modified. It does not need sibling differentiation since no other sibling tool touches custom status, but it also does not explicitly say so.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus alternatives, no preconditions, and no mention of how to clear a status versus set one. The only usage signal is the implied 'change my status,' leaving the agent to infer everything else.

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