Skip to main content
Glama

Oqmd

by io.github.pipeworx-io

Stable Phases

stable_phases
Read-onlyIdempotent

List the ground-state (on-hull) phases of a chemical system — the thermodynamically stable compounds in OQMD for a given set of elements. e.g. "Fe-O" returns FeO, Fe2O3, Fe3O4. Restricts to materials made ONLY of the given elements with stability <= ~0 (on the convex hull). Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax phases, default 15, max 30.
elementsYesA chemical system as dash- or comma-separated elements, e.g. "Fe-O", "Li-Fe-O", "Al,O".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "elements": "Fe-O"
+  },
+  {
+    "elements": "Li-Fe-O",
+    "limit": 20
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Despite annotations already marking readOnly, openWorld, idempotent, and non-destructive, the description adds substantial behavioral context: the stability criterion (<= ~0), the exclusivity of elements, and the 'Keyless' access. This goes well beyond the annotations and informs the agent about filtering behavior and authentication needs.

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 two sentences: the first states the purpose and gives an example, the second adds constraints. Every sentence earns its place, and it is perfectly front-loaded. No wasted words.

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?

The tool has no output schema, but the description provides a concrete example of return values (FeO, Fe2O3, Fe3O4), states the selection criteria, and mentions 'Keyless'. Combined with strong annotations, this is fully complete for an agent to select and invoke the tool correctly.

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%, so the baseline is 3. The description reinforces the 'elements' parameter meaning with an example and emphasizes 'ONLY', but it does not add new syntax, formatting details, or limit constraints beyond what the schema already provides.

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 clearly states the tool lists ground-state (on-hull) phases of a chemical system, with a specific verb ('List'), resource ('phases'), and scope ('thermodynamically stable compounds in OQMD'). The example ('Fe-O' returns FeO, Fe2O3, Fe3O4) solidifies understanding and distinguishes this from sibling tools like search_materials.

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

Usage Guidelines4/5

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

The description implies when to use this tool: to retrieve stable phases for a given element set. It adds the key constraint 'materials made ONLY of the given elements' and notes 'Keyless' (no auth). However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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

All Oqmd toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation2/5

Many tools overlap in purpose: ask_pipeworx, ask_pipeworx_grounded, and deep_research all answer questions; multiple prediction market tools (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk) have subtle distinctions. An agent would struggle to choose correctly among these.

Naming Consistency4/5

Tool names follow a consistent snake_case verb_noun pattern (e.g., list_subscriptions, generate_llms_txt). A few are noun phrases (stable_phases) but the style is uniform and predictable.

Tool Count2/5

33 tools is high for a single server, especially given the mix of two unrelated domains (materials database and general data querying). Many prediction market tools could be consolidated, and the broad scope suggests over-engineering.

Completeness3/5

The materials data side covers search and retrieval adequately. The query side offers many capabilities but has redundant paths (e.g., multiple ways to ask questions) and gaps in editing or updating data. Overall coverage is mixed.

Resources