Bristlecone Logic Utilities
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRISTLECONE_API_KEY | No | Optional API key for authenticated or metered tenant access. Used in the Authorization header as 'Bearer bl_live_YOUR_API_KEY'. If provided, requests are authenticated with this key. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_contentC | Guarded content extraction with SSRF socket pinning. |
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 1 tool
With only one tool, there is no possibility of overlap or confusion. The single tool's purpose is clearly distinct.
The sole tool follows a clear verb_noun pattern (extract_content). Consistency is trivially satisfied with one tool.
A single tool is too few for a server named 'Bristlecone Logic Utilities', which implies a collection of utilities. The scope feels artificially thin.
The tool covers one specific extraction operation, but the 'Utilities' framing suggests other operations (e.g., batch extraction, format options, URL validation) are missing. Notable gaps exist.