Skip to main content
Glama

Get a sending account

get_sending_account
Read-only

Use this when you need one mailbox's or one LinkedIn seat's details, including its signature. A seat also shows its status and its daily and weekly limits with what is left of them. Free.

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": {
      "channel": "<channel>",
      "accountId": "<accountId>"
    },
    "name": "get_sending_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYes`email` for a mailbox, `linkedin` for a LinkedIn seat.
accountIdYesThe account's id: a mailbox's address, or a LinkedIn seat's id as the list of sending accounts gives it.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real value on top: it discloses what comes back (signature, seat status, daily and weekly limits with remaining allowance) and that the call is 'Free' in credit terms — a cost trait the annotations do not express.

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?

Three short sentences, front-loaded with the usage trigger, then the return content, then the cost note. Nothing is redundant with the schema or annotations, and 'Free.' earns its place as a distinct operational fact.

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?

For a two-parameter read-only getter with full schema coverage and no output schema, the description says enough about what is returned (signature, seat status, limits and remaining) to set expectations. A note on error behavior for an unknown accountId would close the only real gap.

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 100% and both parameters (channel enum and accountId) are fully documented in the schema, including where the LinkedIn seat id comes from. The description adds no syntax or format detail beyond restating the mailbox/seat distinction, 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?

States a specific verb ('need ... details') and resource ('one mailbox's or one LinkedIn seat's details'), and clarifies the two channel flavors plus that a signature is included. It implicitly separates itself from the plural listing sibling by emphasizing 'one', but never names an alternative 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?

'Use this when you need one mailbox's or one LinkedIn seat's details' gives a clear triggering condition and the 'one' framing signals this is a single-record fetch rather than a list. There is no explicit when-not or named alternative, so it stops short of a 5.

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