Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_recent_messages

Read-only

Get up to 10 recent messages with conversation, creator, and labels to quickly see what just happened. No pagination or filters; one call gives the full snapshot.

Instructions

Get up to 10 of the most recent messages, each with its conversation, creator and labels. USE WHEN: A quick "what just happened" glance. Pre-joined, so no follow-up calls for creator or conversation names. USE INSTEAD: list_messages whenever you need more than 10, any date range, paging, or a filter other than conversation and language — this tool supports none of those. EXAMPLE: {"conversation_id":"conv-abc"} RETURNS: {results: [{message: {...}, conversation: {...}, creator: {...}, labels: [...]}]}. No total and no paging: the cap of 10 is the whole answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageNoLanguage (optional) - Original language will be used if not provided or not found.
conversation_idNoConversation ID (optional)
response_fieldsNoDot-path allowlist to shrink the response, e.g. ["results.id","total"]. Omit for the full payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.10.0
    • addedInput schema / properties / response_fields
      Added value: +{
+  "description": "Dot-path allowlist to shrink the response, e.g. [\"results.id\",\"total\"]. Omit for the full payload.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only and non-destructive; the description adds the 10-message cap, lack of paging/total, and filter limitations. It does not define the ordering criterion behind 'recent' or error behavior, but covers the important operational boundaries.

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?

Labeled USE WHEN, USE INSTEAD, EXAMPLE, and RETURNS sections make each point scannable and front-loaded. No wasted sentences; every clause adds decision-relevant information.

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?

With no output schema, the RETURNS section supplies the response shape and explicitly disclaims paging/total. Between annotations, schema, and description, an agent has everything needed to call and interpret this tool correctly.

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 already documents all three parameters at 100% coverage, so baseline applies. Description reinforces that conversation_id and language are the only filters and provides a usage example, but adds little per-parameter semantic detail 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?

Clearly states a specific verb+resource: retrieving up to 10 most recent messages with conversation, creator, and labels. Distinguishes from list_messages by count and pre-joined data.

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

Usage Guidelines5/5

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

Explicitly labels USE WHEN and USE INSTEAD, naming list_messages as the alternative and listing conditions (more than 10, date range, paging, other filters). This leaves no ambiguity about tool selection.

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