Skip to main content
Glama
Sign In
mailnotmilk

mailnotmilk

by jrb00013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_status

Retrieve the current presence status for a specified agent ID. Use this to check if an agent is online, away, or unavailable in your automation workflows.

Instructions

Get presence for an agent id.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but does not. It does not mention side effects, error behavior, authentication requirements, or what 'presence' entails. The agent cannot infer if this is a safe read or what happens for invalid agent IDs, leaving a significant transparency gap.

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?

The description is a single sentence that is concise and front-loaded. Every word earns its place, and it avoids redundancy. For a simple getter, this length is appropriate, though it sacrifices detail for brevity.

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?

The tool has one parameter, no output schema, and no annotations, placing the burden on the description. It fails to explain the return value, the meaning of 'presence,' or any constraints. The agent is left without enough context to confidently invoke the tool and interpret the result.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate for the undocumented parameter. It only says 'for an agent id,' which adds minimal semantic value beyond the schema's type and required flag. It doesn't explain the format, scope, or how the ID is used, so the parameter remains under-specified.

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 uses a specific verb 'Get' with a clear resource ('presence' for an agent). It distinguishes from sibling tools like set_status, which implies a read vs. write distinction. However, it doesn't explicitly differentiate from other status-related tools, 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 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 use this tool versus alternatives. The description merely states what it does without any context, prerequisites, or exclusions. In a large sibling set that includes many read tools, this omission leaves the agent uncertain about the appropriate selection.

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