Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

chemical_elements

Look up a chemical element by symbol, name or atomic number and return its mass, category, group and period. Pure CPU, instant.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "chemical_elements"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSymbol, name or atomic number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed2 schema fields changed
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Symbol, name or atomic number",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "q"
+]
  4. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose that the operation is 'Pure CPU' and 'instant', implying deterministic, side-effect-free, no-auth, no-network behavior. It does not say what happens for an unrecognized input (error vs. empty result) or whether symbol matching is case-sensitive, which are the remaining behavioral unknowns for a lookup tool.

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?

Two short sentences with the resource, accepted inputs, and return fields front-loaded; the performance note trails as a secondary detail. Nothing is redundant or padded.

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

Completeness4/5

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

For a one-parameter, annotation-free lookup with no output schema, the description supplies enough to call it correctly and even enumerates the return shape without an output schema. The only gap is absent not-found/error semantics, which is minor at this complexity level.

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?

Schema description coverage is 100% and the single parameter's description ('Symbol, name or atomic number') already fully documents its accepted forms. The description restates the same three forms without adding format details such as case handling or numeric range, so it sits at the baseline rather than adding meaning.

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 names a specific verb ('Look up'), the exact resource ('a chemical element'), the accepted key forms ('symbol, name or atomic number'), and the returned fields ('mass, category, group and period'). No sibling tool in the list overlaps with this domain, so no differentiation is needed and none is missing.

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?

Usage is only implied: the agent can infer that this is a reference lookup for elemental data, and the accepted input forms are stated. There is no explicit when-to-use/when-not framing and no named alternative, though the tool is genuinely singular in this toolset, which limits how much guidance could be given.

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

All GadgetHumans API Hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources