Scientific Calculator

Periodic Table Lookup

calculator_periodic_table

Read-only

Look up element by symbol, name, or atomic number (Z=1–118).

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": {
      "query": "<query>"
    },
    "name": "calculator_periodic_table"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Symbol, name, or atomic number.

Output Schema

Name	Required	Description	Default
`name`	No
`symbol`	Yes
`expression`	Yes
`atomic_number`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds the Z=1–118 domain constraint and identifier formats, but it does not describe lookup failure behavior or other operational details beyond what annotations provide.

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 front-loaded sentence with no wasted wording. It puts the action, resource, accepted inputs, and numeric range in one compact statement.

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

Completeness5/5

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

For a one-parameter lookup tool with full schema coverage, annotations covering safety, and an existing output schema, the description is complete enough. It explains what the tool returns conceptually (an element) and how to query it without needing to restate return fields.

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

Parameters4/5

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

Schema coverage is 100%, and the single query parameter is already documented with examples. The description still adds a useful constraint absent from the schema by bounding atomic-number queries to Z=1–118.

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 states a specific verb ('Look up') and resource ('element'), and it identifies the three accepted identifier types plus the atomic-number range. No sibling tool performs element lookup, so it is clearly distinguishable from the many calculator_* math utilities.

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 accepted input forms are clear, but the description does not explicitly say when to use this tool versus related calculators such as molar mass or stoichiometry, nor does it state when not to use it. Usage is implied by the tool name and description rather than guided.

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

All Scientific Calculator tools Inspect

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.