Mianshi Web3 Jobs Market Data

preview_search

免费试搜：返回最多 5 条匹配岗位，只给 title / company / location / posted / sector，不含官方投递链接与薪资。每个客户端每天 20 次。要用完整字段（含投递链接、薪资、最多 100 条）请调 search_jobs（$0.02/次）。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "preview_search"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes
`sector`	No
`location`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With zero annotations, the description carries the full burden and does so well: it discloses hard result truncation (5 rows), field-level output restrictions (no apply URL, no salary), and a per-client daily quota of 20 calls. These are exactly the behavioral traits an agent needs before invoking, including cost implications of the alternative.

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?

One compact statement, front-loaded with the free-preview framing and the result cap, followed by the field list and the upgrade path. Every clause (cap, fields, quota, alternative, price) carries distinct information with no filler.

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?

For a low-complexity, 3-parameter search with an output schema present, the description covers result limits, output restrictions, quota, and the sibling alternative — enough to call it correctly. The only real gap is undocumented parameter semantics for sector and location, which matters given 0% schema coverage.

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

Parameters2/5

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

Schema description coverage is 0% and the description never explains q, sector, or location — not their expected format, whether sector must come from list_sectors, whether location is free text or a canonical name, or whether sector and location act as filters or are ignored. The heavy lifting on parameters is left entirely to undocumented schema fields.

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?

States a specific verb and resource (免费试搜 / preview search returning up to 5 matching job postings) and immediately delimits scope with the returned fields (title/company/location/posted/sector) versus what is withheld (no apply link, no salary). This makes it clearly distinguishable from search_jobs, whose full-field behavior is named in contrast.

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

Usage Guidelines5/5

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

Explicit routing: use this free tier for a capped preview, switch to search_jobs ($0.02/call) when full fields, up to 100 results, or salary/apply links are needed. The 20-per-client-per-day cap further tells the agent when this tool is not viable and an alternative must be chosen.

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

All Mianshi Web3 Jobs Market Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?