Skip to main content
Glama

Artil — Email, SMS & Messaging for AI Agents

Show agent accounts

status
Read-only

Show the agent account these tools act as, or your workspace's agent accounts when they act as you, with the addresses people reach each one at. An agent account's signedInBy is the address of the member who signed this client in, usually the person you work with.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a safe, read-only, non-destructive, closed-world operation. The description adds useful behavioral context about what is returned: account addresses and the meaning of signedInBy, including that it identifies the member who signed the client in.

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?

The description is two sentences and front-loads the main behavior before explaining signedInBy. It is appropriately sized for a no-parameter status tool, though the first sentence is slightly dense and could be cleaner.

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?

With no parameters, no output schema, and read-only annotations, the description carries most of the burden for explaining return semantics. It does so partially by naming the accounts, addresses, and signedInBy meaning, but it does not fully describe the shape of the response.

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 no parameter semantics burden. The schema itself has 100% description coverage and no inputs to explain.

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: it shows the agent account the tools act as, or the workspace's agent accounts, along with their reachable addresses. It is clear enough to distinguish this identity/account-inspection tool from the message and team siblings, though the phrasing is somewhat convoluted.

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 implies usage by describing two contexts: showing the agent account these tools act as, or showing workspace agent accounts when they act as the user. However, it does not explicitly say when to call this versus alternatives such as team.list, nor does it give when-not-to-use 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