priornerualnet-mcp
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_domain_priorB | Check a dataset + feature->concept prior and report graph statistics. Returns {valid: bool, stats: {...}} or {valid: false, error: ...}. Stats include sparsity density, per-concept fan-in and orphan features. |
| run_priorneuralnet_benchmarkB | Benchmark the prior-constrained network against parameter-matched MLPs. Writes artifacts under |
| inspect_concept_driversC | Return a concept's attribution rank plus its top-k feature drivers. |
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 3 tools
The three tools map to distinct workflow stages: validating a prior, running a benchmark, and inspecting a concept's drivers. The only mild overlap is that run_priorneuralnet_benchmark produces concept_drivers.json, which inspect_concept_drivers also surfaces, but targeted inspection remains clearly separate.
All names use snake_case with a leading verb and domain object (validate_domain_prior, run_priorneuralnet_benchmark, inspect_concept_drivers). The pattern is predictable and readable.
Three tools are well-scoped for a focused research server: validate input, execute benchmark, inspect result. No extraneous tools; though minimal, each earns its place.
Core workflow is covered from prior validation through benchmark execution to concept-driver inspection. Minor gaps exist around run management (listing/retrieving prior runs, cleanup) and prior editing, but agents can work around these via returned paths and run ids.