Skip to main content
Glama

Freedom Agent Mail

login_inbox

Get a fresh token for an existing inbox (tokens expire; inboxes don't).

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": {
      "address": "<address>",
      "password": "<password>"
    },
    "name": "login_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
passwordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 carries the full burden and does disclose a meaningful trait: tokens are ephemeral while inboxes persist, and this only works on pre-existing inboxes. It omits failure behavior, whether prior tokens are invalidated, and what the password authorizes.

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?

A single front-loaded sentence with a useful parenthetical and no wasted wording. The core action and the state constraint both land immediately.

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

Completeness3/5

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

For a two-parameter, no-output-schema tool this is roughly adequate: the action, the precondition (existing inbox), and the reason to call it are covered. It stops short of describing the token returned or error cases for invalid credentials.

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. It only weakly implies that address identifies the existing inbox and that password is a credential; neither parameter is explained, and there is no note on format or whether the address must already exist.

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?

States a specific verb and resource: retrieving a fresh token for an existing inbox. The qualifier 'existing' separates it from create_inbox, though no sibling is named explicitly.

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?

The parenthetical 'tokens expire; inboxes don't' clearly signals the triggering condition (expired or missing token on an inbox that already exists). It implies you should not use this to provision a new inbox, but names no alternative tool.

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