Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_folder_with_messages

Read-only

Retrieve a folder and its direct messages by folder ID. Returns folder details with messages at that level, excluding nested subfolders.

Instructions

Get a folder together with the messages stored directly in it. USE WHEN: Reading a folder’s contents. Only messages at that folder’s own level are returned — nested folders are not walked. USE INSTEAD: get_folder for structure and counts without message bodies. list_messages with folder_id when you need date filtering or paging, which this tool does not support. FIRST: id comes from get_root_folders (field results[].id) — call it first if you don't have one. EXAMPLE: {"id":"folder-abc"} RETURNS: {folder: {...}, messages: [{...}]}. NARROW: pass response_fields ["folder.id","folder.name","messages"] unless you need more — the full payload is much larger.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
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

A5/5.0
Behavior5/5

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

The description discloses non-obvious behavior beyond the read-only annotations: nested folders are not walked, date filtering and paging are unsupported, and the full payload is much larger than the narrow response. It also states the exact return shape, which is valuable since no output schema exists.

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 structured with clear labels and every block adds distinct value: purpose, when, alternatives, dependency, example, return shape, and response narrowing. It is longer than average but earns its length by front-loading the most important 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?

Given only two parameters, no output schema, and safe read-only annotations, the description covers everything needed to invoke the tool correctly: id provenance, response shape, lack of paging/filtering, and a recommended narrow response. No critical invocation context is missing.

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?

With only 50% schema coverage, the description compensates well: it explains where id comes from (get_root_folders results[].id) and gives a concrete response_fields example while warning that the full payload is much larger. This adds meaning the schema does not provide for id and goes beyond the schema's generic response_fields description.

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?

The description opens with a specific verb-resource pair: 'Get a folder together with the messages stored directly in it.' It also distinguishes itself from sibling tools by clarifying that only messages at that folder's own level are returned and nested folders are not walked.

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?

It explicitly provides USE WHEN, USE INSTEAD with named alternatives (get_folder, list_messages), and the conditions that select each. It also tells the agent to call get_root_folders first to obtain the id, which is essential invocation guidance.

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