get_element_properties
Get the properties for a specific EOxElements custom element.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tagName | Yes | The tag name of the element. |
EOxElements
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It simply states 'Get the properties' without disclosing return format, error behavior for invalid tagName, or any edge cases. This is minimal for a simple getter but still lacks useful context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single clear sentence, front-loaded with the verb and resource. No wasted words, appropriate for a simple one-parameter tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity (one parameter, no output schema), the description is minimally viable but incomplete. It does not explain what properties are returned or any failure modes, which would be expected without an output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes tagName as 'The tag name of the element' with 100% coverage. The description adds slight context by tying it to 'a specific EOxElements custom element', but does not enrich parameter meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Get' with a clear resource 'properties for a specific EOxElements custom element'. It distinguishes itself from sibling tools like get_element_attributes by naming the exact aspect being retrieved.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The purpose implies when to use the tool (when needing element properties), but there is no explicit guidance about alternatives or exclusions. It does not mention when not to use it or direct users to sibling tools for other kinds of data.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation5/5
Each tool targets a distinct aspect of an EOxElements custom element (attributes, CSS parts, CSS properties, events, methods, properties, slots, stories), making selection unambiguous. Even get_element_details, which might aggregate information, is clearly named as a full-details option rather than overlapping with the specific aspect getters.
Naming Consistency5/5
All tools follow a consistent get_element_<aspect> pattern, with list_elements as the sole exception, which still uses a verb_noun structure. This uniformity makes the toolset highly predictable and easy to navigate.
Tool Count5/5
With 10 tools, the server is well-scoped for the purpose of exploring EOxElements custom elements. Each tool covers a specific documented aspect, and the count fits comfortably within the ideal 3-15 range.
Completeness5/5
The toolset comprehensively covers the public API surface of a custom element library: listing elements and retrieving all standard web component facets (attributes, properties, methods, events, slots, CSS parts, CSS properties) plus stories and full details. No obvious gaps exist for the documentation purpose.