baselinker-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BASELINKER_TOKEN | Yes | Your BaseLinker API token |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| baselinker_callA | Call any BaseLinker API method and return its JSON response.
|
| baselinker_list_methodsA | List available BaseLinker API methods with name, category, description
and common params. Pass |
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 2 tools
The two tools have completely distinct purposes: one discovers available API methods and the other invokes them. There is no overlap or ambiguity in selecting between them.
Both tools share the baselinker_ prefix and use snake_case, but baselinker_call is a bare verb while baselinker_list_methods follows a verb_noun pattern. This is a minor inconsistency rather than a chaotic naming scheme.
At two tools, this is slightly below the typical 3-15 range, but each tool earns its place for a generic API bridge: one for discovery and one for execution. The count is minimal without feeling incomplete.
The generic baselinker_call provides access to every BaseLinker API method, so there are no missing CRUD or lifecycle operations. The baselinker_list_methods tool covers the discovery gap that would otherwise leave agents guessing at method names.