Retrieve picklist (OptionSet) definitions for a specific entity field, including local and global options, to map allowed values before querying or updating records.
Get OptionSet (enum) definitions for a specific field within an entity. Supports both local and global OptionSets.
| Name | Required | Description | Default |
|---|---|---|---|
| logical_name | Yes | Logical name of the entity | |
| attribute_name | Yes | Logical name of the attribute (field) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral burden. The verb 'Get' signals a read-only retrieval operation, and the local/global OptionSet coverage is disclosed, but permissions, return format, and any rate or response-shape expectations are omitted.
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 two concise sentences with the main purpose front-loaded and no filler. Every sentence contributes useful scope information.
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 two-parameter read tool, the description adequately states the resource being retrieved. However, with no output schema and no annotations, it could give more detail about the returned OptionSet definition shape or how local and global cases differ.
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 schema already explains both parameters as logical names for the entity and attribute. The description does not add format or semantic detail beyond what the schema provides, making the baseline 3 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 states a specific verb and resource: getting OptionSet enum definitions for a specific field within an entity. It also notes support for local and global OptionSets, which adds useful scope. However, it does not explicitly distinguish itself from nearby siblings such as get_model_choices or get_detailed_field_metadata.
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 retrieves picklist options, but gives no explicit when-to-use guidance, prerequisites, or alternatives. The local/global OptionSet note is scope information rather than usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.