Japan Company Info — MCP Server (Free Edition)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_knowledgeC | Search the japan-company-info-free knowledge base |
| get_web_ui_urlA | Get the local Web UI URL for this Orb when GUI mode is enabled |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| unknown/knowledge-base-free-v2.md |
TDQS
Scored across 2 tools
The two tools are entirely distinct: get_web_ui_url retrieves a local UI address while search_knowledge queries a knowledge base. There is no overlap and an agent can easily choose between them.
Both names use a consistent snake_case verb_noun pattern (get_web_ui_url, search_knowledge). The convention is predictable and readable across the set.
Two tools is thin for a company-information server; get_web_ui_url is incidental infrastructure rather than a domain capability. It is borderline rather than clearly mismatched.
The domain implies retrieving Japanese company details, but only a generic knowledge-base search is offered with no structured lookup, listing, or field-specific retrieval. Agents will hit dead ends for anything beyond free-text queries.