field_storage_getRetrieve a single Drupal field storage configuration by its config ID to inspect field settings, storage schema, or debug configuration issues.
Get a single field storage configuration by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| include | No | ||
| config_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'Get' implies a read, but nothing is said about permission requirements, behavior on a missing ID, or any side effects.
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?
A single front-loaded sentence with no wasted words, but it is arguably too terse for the gaps it leaves unaddressed.
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?
An output schema exists so return values need not be described, and this is a simple single-entity read. However, the undocumented 'include' parameter and the absence of any usage or behavioral guidance leave the definition only minimally complete.
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 0% and there are 2 parameters. The description only accounts for config_id ('by ID'); the optional 'include' parameter is left entirely unexplained in both schema and description, leaving an agent to guess its semantics.
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?
States a specific verb (Get), resource (field storage configuration) and scope (single, by ID), which contrasts reasonably with the plural sibling field_storage_list. It does not explicitly name or differentiate from field_config_get or the other field_storage_* CRUD siblings, so it falls short of a 5.
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 phrase 'by ID' implicitly signals this is for retrieving one known entity versus field_storage_list for enumerating all, but there is no explicit when-to-use/when-not guidance and no mention of the list or update/delete alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.