Skip to main content
Glama

Twilio

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Discloses persistence details (scoped by identifier, 24-hour retention for anonymous) beyond annotations. Annotations already indicate idempotent and non-destructive, so description adds context without contradiction.

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?

Front-loaded with purpose, then details. Compact but covers all necessary aspects. Could be slightly tighter, but no wasted words.

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?

Complete for a simple key-value store: explains purpose, when, how, persistence, and pairing with siblings. No output schema needed, and description covers all relevant context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds concrete examples for keys (subject_property, target_ticker) and values (findings, addresses), enriching the schema's generic descriptions.

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?

Provides specific verb ('Save data') and resource ('data the agent will need to reuse later'), with clear examples (ticker, address, preference). Distinguishes from siblings 'recall' and 'forget' by naming 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?

Clearly states when to use ('when you discover something worth carrying forward') and pairs with recall/forget. Does not explicitly state when not to use, but usage context is well-defined.

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

All Twilio toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation2/5

The server is named 'Twilio' but contains only 5 Twilio-specific tools mixed with 31 unrelated Pipeworx tools. An agent must distinguish between Twilio and Pipeworx functionality, and the tool descriptions are clear individually, but the overall set is confusing because the server name implies a focused Twilio service, not a general-purpose data platform with a few Twilio actions.

Naming Consistency2/5

The Twilio tools follow a consistent 'twilio_verb_noun' pattern (e.g., twilio_send_sms, twilio_make_call), while the Pipeworx tools use a separate snake_case convention (e.g., ask_pipeworx, entity_profile, deep_research). The two naming conventions are clearly distinct and do not mix, but the overall set is inconsistent because the server is named after one convention yet the majority of tools follow a different one.

Tool Count1/5

With 36 tools, the count is high, but the critical issue is that only 5 tools are relevant to the Twilio server name. The remaining 31 tools belong to Pipeworx, a completely different domain. This is an extreme mismatch between the claimed server purpose (Twilio) and the actual tool set, making the tool count inappropriate.

Completeness2/5

For a Twilio-focused server, the tool set is very incomplete: it covers only basic SMS sending, call initiation, and listing messages/calls. Missing are phone number management, media handling, conversation features, and other common Twilio operations. The Pipeworx tools are comprehensive for their own domain, but they are irrelevant to the Twilio server's stated purpose, leaving significant gaps.

Resources