Skip to main content
Glama
errajibadr

TwilioManager MCP

by errajibadr
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_regulatory_bundle_sid

Retrieve the regulatory bundle SID for a Twilio subaccount to manage compliance requirements and documentation.

Instructions

Get the regulatory bundle SID for a Twilio subaccount

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subaccount_sidYes

Implementation Reference

  • twilio_manager_mcp.py:97-108 (handler)
    The MCP tool handler function that retrieves the regulatory bundle SID for a given subaccount SID by calling the AsyncTwilioManager helper.
    async def get_regulatory_bundle_sid(subaccount_sid: str) -> str | None:
    """
    Get the regulatory bundle SID for a Twilio subaccount
    Args:
        subaccount_sid: The SID of the Twilio subaccount
    Returns:
        The regulatory bundle SID for the Twilio subaccount
    """
    print(f"Getting regulatory bundle SID for subaccount {subaccount_sid}")
    async with async_twilio_manager:
        return await async_twilio_manager.get_bundle_sid(subaccount_sid)
  • twilio_manager_mcp.py:93-96 (registration)
    The @mcp.tool decorator registering the tool with its name and description.
    @mcp.tool(
    name="get_regulatory_bundle_sid",
    description="Get the regulatory bundle SID for a Twilio subaccount",
)
  • api/async_twilio_api.py:207-216 (helper)
    The AsyncTwilioManager method that implements the core logic: lists all regulatory bundles and returns the SID of the one associated with the given subaccount SID.
    async def get_bundle_sid(self, subaccount_sid: Optional[str] = None) -> Optional[str]:
    """
    Get the bundle SID for a subaccount.
    """
    bundles = await self.client.numbers.v2.regulatory_compliance.bundles.list_async()
    for bundle in bundles:
        if bundle.account_sid == subaccount_sid:
            return bundle.sid
    return None

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action is to 'Get', implying a read operation, but doesn't specify if it requires authentication, rate limits, error conditions, or what the output format might be (e.g., a string SID). This leaves significant gaps in understanding how the tool behaves.

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, clear sentence with no wasted words. It front-loads the key action and resource, making it easy to understand at a glance. Every part of the sentence contributes directly to the tool's purpose.

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

Completeness2/5

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

Given the tool's complexity (a read operation with one parameter), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what a 'regulatory bundle SID' is, how it's used, or what the return value looks like, leaving the agent with insufficient context to use the tool effectively.

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?

The description mentions 'for a Twilio subaccount', which aligns with the single parameter 'subaccount_sid' in the schema. However, schema description coverage is 0%, so the description doesn't add details beyond the parameter's existence, such as format or validation rules. With one parameter and no schema descriptions, the baseline is 3 as it minimally compensates.

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 clearly states the action ('Get') and the resource ('regulatory bundle SID for a Twilio subaccount'), making the purpose understandable. It doesn't explicitly differentiate from sibling tools like 'list_twilio_subaccounts', which lists subaccounts rather than retrieving a specific bundle SID, but the distinction is implied through the specific resource focus.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, such as needing a valid subaccount SID, or comparisons to other tools that might handle regulatory data. Usage is implied only by the tool's name and purpose.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/errajibadr/twilio_manager_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server