scholar-mcp

Search Standards

search_standards

Read-only

Search technical standards by identifier, title, or free text across NIST, IETF, W3C, and ETSI. Optionally filter results by standards body.

Instructions

Search technical standards by identifier, title, or free text.

Searches NIST, IETF, W3C, and ETSI. Use body to restrict to one source body.

A cold catalogue makes this slow: the first call after a fresh install or a cleared cache downloads and parses each body's index, which runs well past the soft deadline. Such a call returns a job handle to poll with get_job_result rather than the result itself.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	No	Optional filter — "NIST", "IETF", "W3C", or "ETSI".
`limit`	No	Maximum results (max 50).
`query`	Yes	Identifier, title, or free text.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.10.0Sep 8, 2026
- addedOutput schema / additionalProperties
```
Added value: +true
```
- removedOutput schema / properties
```
Removed value: -{
-  "result": {
-    "type": "string"
-  }
-}
```
- removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```
- removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```
First observedv1.9.0Aug 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description explicitly discloses that a cold cache can cause the first call to exceed the soft deadline and that such calls return a job handle instead of the result, directing the agent to poll with `get_job_result`. This goes beyond the annotations (readOnly, openWorld) and provides critical runtime behavior.

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 paragraph that leads with the core purpose, then lists sources, explains the body parameter, and concludes with the performance caveat. It is concise, well-organized, and free of redundant text.

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 description includes the essential information needed to invoke the tool correctly: what it searches, the set of sources, the optional filter, and the potential asynchronous behavior on first use. Given the tool's simplicity and the presence of an output schema, this is sufficient for an agent to use it effectively.

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?

The schema already provides descriptions for all three parameters (query, body, limit) with 100% coverage. The description reiterates the body parameter's purpose and the query types, but adds no new semantic information beyond the schema. Baseline for full schema coverage is 3.

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 that the tool searches technical standards by identifier, title, or free text across NIST, IETF, W3C, and ETSI. It distinguishes from sibling search tools (search_books, search_papers) by specifying the subject domain and source bodies.

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 indicates when to use the tool (to search standards) and provides guidance on using the `body` parameter to restrict to a single source body. It also warns about the first call being slow and possibly returning a job handle, guiding the agent on handling asynchronous responses. However, it does not explicitly contrast with alternative search tools, so it is clear but not exhaustive.

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