Baike-Render
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| request_baikeD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| render_baike_to_html |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'request_baike' stands alone with no competing alternatives for an agent to confuse it with.
A single tool inherently has perfect naming consistency, as there are no other tool names to compare it against. The tool name 'request_baike' follows a clear verb_noun pattern, but consistency cannot be assessed across a set of one.
A single tool is too few for most server purposes, as it severely limits functionality and suggests the server may be incomplete or trivial. Without a description, it's unclear if this minimal surface is justified, but typically one tool indicates under-scoping.
With only one tool and no description, it's impossible to assess coverage of any domain. The server appears severely incomplete, as a single 'request_baike' tool likely cannot handle a full workflow or lifecycle for Baike-related tasks, leaving obvious gaps.