NEMAD MCP

nemad_formula_search

Read-only

Search NEMAD by exact chemical formula (e.g., Fe2O3) across selected material databases, then cache paginated results for reuse.

Instructions

Search NEMAD by exact chemical formula (for example Fe2O3), then cache results.

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": {
      "database_type": "<database_type>",
      "formula": "<formula>"
    },
    "name": "nemad_formula_search"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`formula`	Yes
`database_type`	Yes

Output Schema

Name	Required	Description	Default
`count`	Yes	Matches NEMAD returned, capped by limit; not the database total.
`cache_key`	Yes
`next_step`	No		Call nemad_read_results with cache_key to read a page of results.
`database_type`	Yes
`results_returned`	Yes
`expires_in_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 9, 2026

TDQS

B3.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=true, so the safety profile is covered. The description adds one genuinely new behavioral fact: results are cached. However, it does not say where or how long they are cached, whether a cache hit changes the response, or whether repeated calls are deduplicated.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the matching mode and example come first. It is efficient, though its brevity is partly the cause of the missing parameter and alternative guidance.

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

Completeness2/5

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 explained. But for a three-parameter tool with zero schema descriptions, the definition leaves the database_type enum and limit semantics undocumented and the caching side effect unexplained, which is not enough for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, yet it only glosses "formula" (via the Fe2O3 example). The required database_type enum with four values (magnetic, magnetic_anisotropy, thermoelectric, superconductor) and the limit parameter with default 100 are completely unaddressed.

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

Purpose4/5

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

States a specific verb ("Search") and resource (NEMAD) plus the matching mode ("exact chemical formula") with a concrete example, Fe2O3. It does not name the sibling nemad_search or explain how it differs from a general NEMAD search, so differentiation is implied rather than explicit.

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 word "exact" implies a constraint (no partial/substring matching), which is a weak usage signal, but there is no explicit statement of when to choose this over nemad_search or nemad_read_results. No prerequisites, no exclusions, no follow-up guidance after caching.

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

Deploy Server