list_contentsRetrieve records stored directly inside a specific space or box by providing its stable parent ID, enabling quick inventory checks without scanning nested containers.
List records directly inside a space or box using an external or stable parent ID.
| Name | Required | Description | Default |
|---|---|---|---|
| parentId | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the operation read-only and non-destructive. The description adds behavioral value by scoping results to records 'directly inside' the container, implying non-recursive traversal, and by clarifying that the parent ID is external/stable rather than an internal key.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The entire description is a single front-loaded sentence that conveys action, object scope, and parameter type with no filler. Every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only list operation with one parameter, the description plus annotations cover safety and scope. It does not detail the return value's shape or pagination, but the title and 'List records' phrase adequately convey the expected result for a basic tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage and only one parameter, the description must add meaning, and it does: parentId is an external or stable identifier for a space or box. It does not specify the ID format or how to obtain it, but for a single-parameter tool this is reasonable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific action ('List records directly inside a space or box') and a distinctive input ('external or stable parent ID'). This clearly differentiates it from siblings like search_inventory and get_inventory_object, which target search or single-object retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool should be used when you need direct child records of a container and have a parent ID, but it does not explicitly state when to prefer it over search_inventory or get_inventory_object. No exclusions or alternative routing are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.