Skip to main content
Glama
AgenticMail

AgenticMail

Official
by agenticmail

sms_config

Check an agent’s SMS configuration to confirm whether SMS is enabled and retrieve the assigned phone number and forwarding email.

Instructions

Get the current SMS/phone number configuration for this agent. Shows whether SMS is enabled, the phone number, and forwarding email.

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

Input Schema

NameRequiredDescriptionDefault
_accountNoOptional. Override identity for THIS call: pass the AgenticMail agent name (e.g. "Fola") to authenticate as that agent. Requires AGENTICMAIL_ACCOUNT_KEYS_JSON to contain a matching key. Omit to use the default identity (AGENTICMAIL_API_KEY).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.104
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.9.101
  3. Removedv0.9.89
  4. Addedv0.9.73
  5. Removedv0.9.69
  6. Addedv0.9.35
  7. Removedv0.9.31
  8. Addedv0.9.12
  9. Removedv0.9.11
  10. Changed2 schema fields changedv0.5.63
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / _account
      Added value: +{
      +  "description": "Optional. Override identity for THIS call: pass the AgenticMail agent name (e.g. \"Fola\") to authenticate as that agent. Requires AGENTICMAIL_ACCOUNT_KEYS_JSON to contain a matching key. Omit to use the default identity (AGENTICMAIL_API_KEY).",
      +  "type": "string"
      +}
  11. First observedv0.5.59

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does establish this is a non-mutating read that reports current state. It does not state permission requirements, behavior when SMS was never configured (empty vs. error), or how the identity override affects results. The disclosure of returned fields is helpful but not a complete behavioral picture.

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?

Two short sentences, purpose front-loaded, with the second sentence adding the concrete return fields rather than restating the name. No filler or hedging; only minor room to fold in alternative-tool guidance without bloat.

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 zero-required-parameter read tool with no output schema, the description is essentially sufficient: it says what is fetched and what the response contains. The remaining gap is minor — no statement of what happens when SMS is not yet set up.

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?

There is a single optional parameter (_account) whose schema description is fully documented at 100% coverage, so the baseline is 3. The description adds nothing about the identity override or its implications for which agent's configuration is read, so it does not exceed the schema.

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 names a specific verb and resource ('Get the current SMS/phone number configuration for this agent') and enumerates the three fields it surfaces (enabled flag, phone number, forwarding email), so the agent knows exactly what it returns. It does not explicitly distinguish itself from the similar sibling telegram_config, which keeps it 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 Guidelines3/5

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

Usage is implied rather than stated: 'current' and 'Get' signal a read-only inspection of existing settings, contrasting with setup-oriented siblings like sms_setup. There is no explicit when-to-use, when-not-to-use, or named alternative for checking other channels (e.g. telegram_config).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.