Skip to main content
Glama
theYahia

@theyahia/voximplant-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_sms_history

Get SMS logs for a specified time period, with optional filters on sender and receiver numbers to isolate specific message threads.

Instructions

Получить историю SMS-сообщений за период с фильтрами по номерам.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoКоличество записей (1..200)
offsetNoСмещение (offset)
to_dateYesКонец периода (YYYY-MM-DD HH:mm:ss, UTC)
from_dateYesНачало периода (YYYY-MM-DD HH:mm:ss, UTC)
source_numberNoФильтр по номеру отправителя
destination_numberNoФильтр по номеру получателя

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • addedInput schema / properties / count / description
      Added value: +"Количество записей (1..200)"
    • changedInput schema / properties / from_date / description
      Previous value: -"Начало периода (YYYY-MM-DD HH:mm:ss)"New value: +"Начало периода (YYYY-MM-DD HH:mm:ss, UTC)"
    • addedInput schema / properties / offset / description
      Added value: +"Смещение (offset)"
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / to_date / description
      Previous value: -"Конец периода (YYYY-MM-DD HH:mm:ss)"New value: +"Конец периода (YYYY-MM-DD HH:mm:ss, UTC)"
  2. First observedv1.2.3

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'get history', which implies a read operation, but it does not disclose pagination behavior, result shape, read-only side effects, timezone nuances, or limitations. It adds little beyond what the tool name already suggests.

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?

The description is a single short sentence with no filler. It states the core action and scope immediately, which is an economical structure.

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?

Given the moderate complexity (6 params) and full schema coverage, the description is minimally adequate for invoking the tool but omits contextual help such as the output shape, clarification of standard SMS vs A2P, and relationship to sibling get_a2p_sms_history. The agent may need to probe the API to learn expected return structure.

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 the input schema already fully describes each parameter. The description rephrases the date range as 'period' and the number filters as 'фильтрами по номерам', but it does not add additional semantics such as numeric ranges, defaults, or format behavior that are not already in 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 states the verb/resource clearly: 'get SMS message history over a period with filters by numbers'. This is easy to parse and distinguishes from call-history siblings. However, it does not explicitly differentiate from the sibling get_a2p_sms_history, so it misses one point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus alternatives. The description does not mention get_a2p_sms_history, send_sms, or any conditions that would select this tool over sibling tools. The agent must infer usage solely from the name and filters.

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