Skip to main content
Glama

Ieee Standards

by io.github.pipeworx-io

Ieee Standard Search

ieee_standard_search
Read-onlyIdempotent

Search IEEE STANDARDS by number or topic and get each standard's title, abstract/scope, publication year, DOI and IEEE Xplore link. Covers the IEEE standards catalogue: IEEE 802.11 Wi-Fi / wireless LAN, IEEE 802.3 Ethernet, IEEE 1588 PTP precision time protocol, IEEE 1547 distributed energy resource interconnection, IEEE 1149.1 JTAG boundary scan, IEEE 754 floating point, IEEE 802.1AS timing, and the rest. Answers "what does IEEE standard X cover", "which IEEE standard defines Y", "find the IEEE 802.3 ethernet spec", "latest revision of IEEE 1588". Returns metadata plus the abstract; the normative clause text is sold by IEEE, so follow html_url to purchase or access it. Requires your own free IEEE Xplore API key via _apiKey (register an app at developer.ieee.org). Example: ieee_standard_search({ query: "802.11 wireless LAN", limit: 5, _apiKey: "your-ieee-key" }). Example: ieee_standard_search({ query: "1588 precision time protocol", year: 2019, _apiKey: "your-ieee-key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoRestrict to standards published in this year, e.g. 2020 (optional).
limitNoMax standards to return (default 10, max 50).
queryYesStandard number and/or topic keywords, e.g. "802.11 wireless LAN", "1588 precision time protocol", "802.3 ethernet", "1547 distributed energy resources", "754 floating point arithmetic".
_apiKeyYesYour IEEE Xplore Metadata API key, sent as the `apikey` query param. Free — register an app at https://developer.ieee.org. Approval can take a few business days, and a new key stays inactive until IEEE activates it.
start_recordNo1-based offset for paging through a large result set (default 1).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds key behavioral context: requires an API key (with activation delay), explains that full text is behind a paywall, and describes output fields. No contradiction with annotations.

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?

The description is compact at ~120 words, front-loading the core purpose. It uses examples effectively. Slightly verbose in the examples repetition, but overall efficient for the information conveyed.

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?

Despite no output schema, the description explicitly lists return fields and the limitation on full text. It covers all parameters, prerequisites (API key), and use cases. For a search tool with good annotations and 100% parameter coverage, this is highly complete.

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

Parameters5/5

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

Schema coverage is 100%, with each parameter described. The description enhances understanding by providing real examples for query and year, and detailed guidance on _apiKey (registration, activation). This adds significant value beyond the schema.

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 specifies the resource ('IEEE STANDARDS'), action ('Search by number or topic'), and returned fields ('title, abstract/scope, publication year, DOI and IEEE Xplore link'). It includes specific examples (e.g., '802.11 wireless LAN') and distinguishes from sibling tools like ieee_article and ieee_search by focusing on standards.

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 provides example queries and explicitly states what questions it answers (e.g., 'what does IEEE standard X cover'). It explains limitations (normative text sold) and prerequisites (API key). However, it does not directly compare to sibling tools like ieee_search, leaving the agent to infer when to use this vs. alternatives.

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

All Ieee Standards 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

Several tools blur together: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer factual questions with overlapping routing behavior, while polymarket_edges, polymarket_arbitrage, and bet_research all surface prediction-market opportunities. Long descriptions help, but the boundaries between these clusters are genuinely unclear, and the three IEEE tools are buried in a sea of unrelated Pipeworx tools.

Naming Consistency4/5

The naming is predominantly snake_case with clear family prefixes like ieee_, ask_pipeworx_, and polymarket_, and most tools follow a readable verb_noun or noun_verb shape. Minor deviations exist (remember/recall/forget, bet_research, pipeworx_trending) but there is no camelCase/mixed-convention problem, so the overall pattern is predictable.

Tool Count1/5

A server named 'Ieee Standards' exposes 34 tools, yet only three of them (ieee_search, ieee_standard_search, ieee_article) actually serve that domain. The remaining 31 tools form a general Pipeworx data, prediction-market, memory, and subscription platform, which is an extreme scope mismatch for the stated server purpose.

Completeness4/5

For the IEEE lookup domain, the three IEEE tools cover the core read-only workflow: broad corpus search, standards-specific search, and full metadata retrieval by article number or DOI. Minor gaps exist (browsing by committee, revision/status history, full-text access) but those are workable or inherently restricted by IEEE's paywall.

Resources