Skip to main content
Glama

chemical_elements

Retrieve comprehensive data on chemical elements, including atomic properties and classifications, for educational or reference use.

Instructions

chemical elements — Other Utilities tool. Costs $0.001 USDC via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNoTool parameters as JSON object
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of disclosing behavior. It mentions a cost of $0.001 USDC, which is a small behavioral detail, but omits any information about return values, side effects, or required inputs, leaving the tool's operation completely opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short, but this is under-specification rather than effective conciseness. The only informative phrase is the cost, which does not justify the description's existence; it fails to provide any actionable content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, no annotations, and the parameter schema is generic. The description should at least state the tool's function and usage, but instead gives only a category label and cost, making it completely inadequate for a tool with this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema defines a single generic 'params' object with no meaningful parameter fields. The description adds no clarification about what parameters should be passed, so the tool remains unusable without external documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description merely restates the tool name and categorizes it as 'Other Utilities,' providing no verb or specific function. It does not indicate what actions the tool performs with chemical elements, making it a tautology.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus any alternative. It only mentions a cost, which is irrelevant for selection without knowing the tool's purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gadgethumans-dev/gadgethumans-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server