B2Bhint MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API 密钥 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_person_by_nameC | Search for a person by parameters will return a list of persons that match your query |
| get_company_full_dataC | The Get company details endpoint will return all full company data, including company contacts, financial reports and other data |
| search_company_by_nameC | Search for a company by parameters will return a list of companies that match your query |
| get_company_basic_dataC | The Get company details endpoint will return all basic company data on B2BHint. |
| search_company_by_emailC | Search for a company by email will return a list of companies that match the selected email |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no ambiguity: get_company_basic_data and get_company_full_data target different levels of company detail, while the three search tools each target different search criteria (email, company name, person name). The descriptions reinforce these distinctions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with snake_case: get_company_basic_data, get_company_full_data, search_company_by_email, search_company_by_name, and search_person_by_name. The naming is predictable and readable throughout the set.
With 5 tools, this server is well-scoped for its apparent domain of B2B company and person data retrieval. Each tool earns its place by covering distinct operations (basic/full data retrieval and multiple search types), avoiding bloat or thinness.
The tool set provides strong coverage for data retrieval and search in the B2B domain, with no dead ends. A minor gap exists in update/delete operations (e.g., no tools for modifying company data), but agents can likely work around this given the server's focus on querying.