Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

get_message_history

Retrieve message history from multiple integrated services, optionally filtering by date to track conversations and interactions across platforms.

Instructions

List message history optionally since a date

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_dateNo

Implementation Reference

  • The handler function for the 'get_message_history' tool. It checks configuration, extracts the optional 'from_date' from input args, and delegates to the Twilio client's getMessageHistory method.
    async get_message_history(args: Record<string, unknown>) {
      if (!cfg.twilioAccountSid || !cfg.twilioAuthToken) throw new Error("TWILIO_ACCOUNT_SID/TWILIO_AUTH_TOKEN are not configured");
      const fromDate = args.from_date ? String(args.from_date) : undefined;
      return client.getMessageHistory(fromDate);
    },
  • The registration of the 'get_message_history' tool in the tools array, including name, description, and input schema.
    {
      name: "get_message_history",
      description: "List message history optionally since a date",
      inputSchema: {
        type: "object",
        properties: { from_date: { type: "string" } },
      },
    },
  • Input schema for the 'get_message_history' tool, defining an optional 'from_date' string property.
    inputSchema: {
      type: "object",
      properties: { from_date: { type: "string" } },
    },
  • Helper method in TwilioClient class that makes the API request to retrieve Twilio message history, optionally filtered by DateSent query parameter.
    getMessageHistory(fromDate?: string) {
      return this.request(`/Accounts/${this.accountSid}/Messages.json`, {
        headers: { Authorization: `Basic ${this.authHeader}` },
        query: fromDate ? { DateSent: fromDate } : undefined,
      });
    }
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to do so. It doesn't mention whether this is a read-only operation, if it requires authentication, what the output format is, or any rate limits. The description is too vague to inform the agent about behavioral traits.

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, efficient sentence that front-loads the core purpose ('List message history') and adds a key detail ('optionally since a date') without any wasted words. It's appropriately sized for the tool's simplicity.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'message history' entails, the return format, or any behavioral aspects like pagination or errors. For a tool with no structured support, this leaves significant gaps for the agent.

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

Parameters2/5

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

The schema description coverage is 0%, so the description must compensate but adds minimal value. It mentions 'optionally since a date' which hints at the 'from_date' parameter's purpose, but doesn't specify the date format, timezone, or any constraints, leaving the parameter poorly documented.

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 verb ('List') and resource ('message history'), making the purpose specific and understandable. It distinguishes itself from siblings by focusing on message history retrieval, though it doesn't explicitly differentiate from potential similar tools like 'get_sources' or 'search_pages' that might also retrieve messages.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions optional date filtering but doesn't specify scenarios, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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/TaylorChen/muti-mcps'

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