Skip to main content
Glama

Ieee Search

ieee_search
Read-onlyIdempotent

Search the FULL IEEE Xplore corpus — IEEE and IET journal articles, conference proceedings, magazines, books, courses and standards — returning title, authors, abstract, publication venue, year, DOI and the IEEE Xplore link. The broad engineering / computer-science research tool: IEEE paper search, engineering research paper lookup, conference proceedings search, literature review on a technical topic, tracking one author's IEEE publications. Set content_type to focus on a single kind of record ("Conferences", "Journals", "Standards", "Magazines", "Books", "Courses", "Early Access"), or omit it to search every type at once. Returns metadata plus the abstract; the full text is sold by IEEE, so follow html_url to purchase or read it under an institutional subscription. Requires your own free IEEE Xplore API key via _apiKey (register an app at developer.ieee.org). Example: ieee_search({ query: "federated learning edge devices", limit: 10, _apiKey: "your-ieee-key" }). Example: ieee_search({ query: "millimeter wave beamforming", content_type: "Conferences", year: 2024, _apiKey: "your-ieee-key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoRestrict to this publication year, e.g. 2024 (optional).
limitNoMax records to return (default 10, max 50).
queryYesFree-text search across IEEE metadata (title, abstract, index terms), e.g. "federated learning edge devices", "lithium-ion battery state of charge estimation".
authorNoRestrict to an author name, e.g. "Yoshua Bengio" (optional).
_apiKeyYesYour IEEE Xplore Metadata API key, sent as the `apikey` query param. Free — register an app at https://developer.ieee.org.
sort_byNoSort field (default relevance).
sort_orderNoSort direction (default desc when sorting by publication_year, asc otherwise).
index_termsNoRestrict to an IEEE or author index term, e.g. "Deep learning" (optional).
content_typeNoRestrict to one IEEE content type (optional). Omit to search every content type at once.
start_recordNo1-based offset for paging through a large result set (default 1).
publication_titleNoRestrict to a journal or proceedings title, e.g. "IEEE Transactions on Antennas and Propagation" (optional).

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, non-destructive. The description adds concrete behavioral details: requires a free IEEE Xplore API key, that full text is sold by IEEE with a link to access, and that the tool returns metadata plus abstract. No contradictions 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 fairly long but well-structured: main purpose first, then returned fields, usage contexts, parameter guidance, authentication warning, and examples. It is front-loaded and each part adds value. Could be slightly more concise, but not overly verbose.

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?

Given 11 parameters and no output schema, the description covers key aspects: corpus scope, returned fields, authentication, paywall, parameter usage, and examples. It does not explain the return format in detail (e.g., JSON structure) but that is partly covered by saying what fields are returned. Overall sufficient for an experienced developer.

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%, so baseline 3. The description adds value by explaining the content_type parameter's options and their effect ('focus on a single kind of record' vs 'search every type'), and provides two examples showing parameter usage. This goes beyond the schema's enum description.

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?

Clearly states the tool searches the full IEEE Xplore corpus and enumerates the content types (journal articles, conference proceedings, etc.) and returned fields (title, authors, abstract, DOI, link). The phrase 'FULL IEEE Xplore corpus' distinguishes it from siblings like ieee_article or ieee_standard_search, which are more specific.

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?

Provides explicit usage contexts: 'The broad engineering / computer-science research tool: IEEE paper search...' and explains when to use content_type parameter vs omit. Does not directly mention alternatives like ieee_article but the sibling names and description imply it. No when-not-to guidance, but the context is clear.

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

Try in Browser

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.