Skip to main content
Glama
priornerualnet-mcp

priornerualnet-mcp

by LatentVirtue

validate_domain_prior

Checks whether a dataset and its feature-to-concept prior are valid, then reports sparsity density, per-concept fan-in, and orphan features.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "data_path": "<data_path>",
      "prior_path": "<prior_path>",
      "target_column": "<target_column>"
    },
    "name": "validate_domain_prior"
  }
}

Input Schema

NameRequiredDescriptionDefault
data_pathYes
prior_pathYes
target_columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden, and it does disclose the return shape ({valid, stats} or {valid: false, error}) plus what the stats contain (sparsity, per-concept fan-in, orphan features). It does not say whether any files are written, what permissions or formats are needed, or how large a dataset it can handle, which matters for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the outcome and followed by the return contract; nothing is redundant. The stat list is compact but earns its place as an output hint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the return-value summary in the description is genuinely useful. However, leaving target_column undefined and file formats unspecified means an agent cannot reliably form the call from this definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all three parameters are required, so the description must compensate. It hints that data_path is the dataset and prior_path is the prior, but target_column is never mentioned and no file-format or expected-structure details are given for any parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: checks a dataset plus a feature->concept prior and reports graph statistics. That is enough for an agent to distinguish it from inspect_concept_drivers and run_priorneuralnet_benchmark, though the description never explicitly contrasts them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus the sibling tools, no prerequisite or ordering guidance (for example, whether it should run before a benchmark), and no exclusions. An agent must infer the validation role from the verb alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.