Technical Spec Search
Full-text search with extracted specifications; numeric queries like "50 Nm" match.
Full-text search over abstracts and full texts, with extracted technical specifications (values, ranges, tolerances, units). Numeric constraints like "50 Nm" are matched.
What agents use it for
- Find components meeting a spec
- Look up measured values with sources
- Engineering research
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | yes | Words and optional numeric constraints, e.g. 'torque sensor 50 Nm' |
category | "general" | "tech_specs" · default "tech_specs" | no | Result category: tech_specs (specification tables) or general |
topic | string | no | Topic slug from list_topics, e.g. laser-calibration |
year_from | integer | no | Earliest publication year to include |
limit | integer · default 10 | no | Maximum number of results to return |
Call it
{
"name": "search_specs",
"arguments": {
"query": "torque sensor 50 Nm"
}
}curl -i -X POST "https://api.ishob.com/v1/search" \
-H "Content-Type: application/json" \
-d '{"query":"torque sensor 50 Nm"}'Paid with x402: the first call returns HTTP 402 with the price; an x402 client (for example @x402/fetch or @x402/mcp) signs a USDC payment and retries. Calls that fail are not charged.
Connect the MCP server: setup for Claude, Cursor and other clients.