list_propertiesRetrieve all property and column definitions for a given collection by its ID, enabling you to inspect the schema before reading or updating documents.
List all property (column) definitions for a collection.
| Name | Required | Description | Default |
|---|---|---|---|
| collectionId | Yes | ID of the collection (database) |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. The word "List" and phrase "all property definitions" imply a read-only, complete enumeration operation, but the description does not explicitly state read-only safety, permissions, or whether results are paginated.
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 description is a single efficient sentence with no wasted words, and the core action and scope are front-loaded.
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 tool with one required, fully documented parameter and no output schema, the description is largely complete. It could be slightly stronger by clarifying read-only behavior or result completeness, but nothing essential is missing.
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?
Schema description coverage is 100%, so the single collectionId parameter is already fully documented as "ID of the collection (database)." The description reinforces that properties belong to a collection, but adds no syntax, format, or validation details beyond the schema.
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 states a specific verb and resource: "List all property (column) definitions for a collection." This is clear and distinguishes it from siblings like list_collections, list_documents, add_property, and delete_property, though it does not explicitly name those alternatives.
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?
Usage is implied by the description: use this to inspect schema/property definitions for a known collection. However, there is no explicit guidance on when to use this versus list_collections, list_documents, or other sibling tools, and no stated prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.