get_settingsRetrieve OpenCart store configuration by group or key pattern to inspect specific settings. Filter results using SQL LIKE for targeted configuration queries.
Get OpenCart settings. Filter by group (e.g. 'config') and/or key pattern (SQL LIKE).
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | ||
| group | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral burden. While 'Get' implies a read, the description does not explicitly state read-only safety, auth requirements, rate limits, or side effects; it only describes the key-pattern matching behavior.
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?
Two sentences, front-loaded with the core purpose and then filter details. There is no redundant text, and every sentence contributes directly to understanding the tool.
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. The description covers purpose and parameter filtering, but it omits when-to-use guidance and read-only/auth context for a tool that has no annotations.
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%, so the description must compensate for both parameters. It explains that group filters by group (e.g. 'config') and key supports a SQL LIKE pattern, adding useful meaning, though it does not clarify that empty defaults likely mean no filter.
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') and resource ('OpenCart settings'), and describes the filtering capability. However, it does not name or distinguish sibling tools such as get_j3_settings or get_j3_skin_settings, so sibling differentiation is left implicit.
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 explains available filters but gives no when-to-use guidance, alternatives, or prerequisites. An agent must infer that this is the default settings getter rather than one of the J3-specific or generic query siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.