Skip to main content
Glama
Sign In
GoldBean

GoldBean

by wuzenghai616-lang
OverviewSchemaSourceRelated ServersDiscussions(4)Admin
JavaScript
Remote

baidu_reranker

Rerank documents by relevance to a query using BCE-Reranker. Provide query and document list (separated by ||) for improved ranking results.

Instructions

[NLP] 重排序（BCE-Reranker） — $0.01/call (free: 5/5 today)

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": {
      "query": "<query>",
      "documents": "<documents>"
    },
    "name": "baidu_reranker"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes查询词
documentsYes文档列表(用||分隔)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are provided, and the description only includes pricing information. It does not disclose behavioral traits such as read-only nature, rate limits, or authorization requirements. The agent gets no behavioral insight beyond the bare name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short but at the expense of useful information. It is under-specified rather than concise. A better description would provide purpose and usage in a few sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has two required parameters and no output schema, the description is incomplete. It does not explain what reranking does, how the output is formatted, or in what scenarios it should be used. The agent lacks essential context to use the tool correctly.

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?

Schema description coverage is 100%, with clear Chinese descriptions for both parameters ('query term' and 'document list separated by ||'). The description adds no additional meaning beyond what the schema already provides, so it meets the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description labels the tool as '重排序（BCE-Reranker）' which indicates reranking, but does not explain what it does clearly in English or NLP terms. It is vague and does not distinguish it from sibling tools like baidu_nlp.

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

Usage Guidelines1/5

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

No usage guidelines are provided. The description does not specify when to use this tool versus alternatives, nor does it give any context on prerequisites or exclusions.

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

Deploy Server

Other Tools