sitecore_personalize_dataset_getRetrieve metadata and schema for a dataset by providing its unique ID, enabling quick access to dataset structure and configuration.
Retrieves metadata and schema information for a single dataset by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| datasetId | Yes | The unique identifier of the dataset. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral transparency burden. 'Retrieves' clearly indicates a non-mutating read operation, and specifying 'metadata and schema information' gives some sense of the returned content. However, it does not disclose authentication requirements, error behavior, or any side-effect-free guarantees beyond the verb itself.
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 sentence with no filler, and the essential facts—what it retrieves and how the dataset is identified—are front-loaded. Every word contributes value.
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 tool with one required, well-documented parameter and no output schema, the description covers the core behavior and return content sufficiently. It is slightly incomplete in that it does not route the agent to the sibling list tool when the ID is unknown, but that is a minor gap for such a simple operation.
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?
The sole parameter is already fully documented in the schema with type, minLength, and a clear description. The description's 'by ID' adds no new meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.
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 verb ('retrieves'), a specific resource ('single dataset'), and the access path ('by ID'), which clearly distinguishes it from the sibling dataset_list operation. It also tells the agent the exact kind of data returned: metadata and schema information.
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 usage: use this when you need metadata/schema for one dataset and already have its ID. It does not explicitly mention when not to use it or point to dataset_list for enumeration, so the guidance is inferred rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.