Skip to main content
Glama
Arsel MCP Server

Arsel MCP Server

Official
by Arsel-SA

List SMS Senders

list-sms-senders
Read-onlyIdempotent

Retrieve your organization's approved SMS sender names, each sender's destination country and registered purposes. Use it to choose a valid sender name with marketing purpose for an SMS campaign.

Instructions

List the organization's approved SMS sender names, the country each one sends to and what it is registered for. Use a sender_name as an SMS campaign's from; campaigns need a sender whose purposes include marketing. Don't read ids or timestamps back to the user unless they ask for them.

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": "list-sms-senders"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoCursor for the next page: the `id` of the last item on this page. Cannot be combined with `before`.
limitNoItems per page, 1-100. Defaults to 20.
beforeNoCursor for the previous page: the `id` of the first item on this page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely non-structured behavior: how to present results ("Don't read ids or timestamps back to the user unless they ask") and the meaning of the `purposes` field for eligibility. Pagination behavior itself is left to the schema.

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 resource description, then integration guidance, then presentation guidance. No redundant restatement of the title or annotations, and every sentence carries a distinct instruction.

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

Completeness5/5

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

There is no output schema, and the description compensates by naming the three meaningful fields returned (sender names, destination country, purposes). Combined with the annotations and the fully documented pagination parameters, an agent has everything needed to call and interpret this tool.

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 description coverage is 100%, and the three parameters (after, before, limit) are fully documented in the schema including the mutual-exclusion constraint. The description says nothing about cursors or page size, which is acceptable at this coverage level but adds no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise verb and resource ("List the organization's approved SMS sender names") and enumerates the returned fields: country and registration purposes. That resource-level specificity cleanly separates it from siblings like list-sms-campaigns or list-sms-messages without needing to name them.

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?

It gives concrete downstream usage rather than mere context: use a returned `sender_name` as a campaign's `from`, and the sender must have `marketing` in `purposes`. That effectively tells the agent why to call this before creating a campaign. It stops short of explicit when-not-to-use or naming an alternative tool, so it is not a full 5.

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