HUMMBL MCP Server

Audit HUMMBL Model References

audit_model_references

Audit HUMMBL model references to verify existence, transformation alignment, and identify duplicates.

Instructions

Audit a list of HUMMBL model references for existence, transformation alignment, and duplicates.

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": {
      "items": "<items>"
    },
    "name": "audit_model_references"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes

Output Schema

Name	Required	Description	Default
`methodologyId`	Yes
`documentVersion`	Yes
`totalReferences`	Yes
`validCount`	Yes
`invalidCount`	Yes
`issues`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.3May 4, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / items / items / additionalProperties
```
Removed value: -false
```
Addedv1.0.0Jan 3, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions checking existence, alignment, and duplicates, but does not disclose side effects, error handling, or whether it is read-only. The transparency is minimal.

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

Conciseness5/5

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

The description is a single, fully front-loaded sentence. It is appropriately sized with no fluff or redundancy.

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

Completeness2/5

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

The tool has a nested parameter and an output schema, but the description does not mention the return value, error scenarios, or any prerequisites. Information is incomplete for an agent to understand the tool's full behavior.

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

Parameters1/5

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

The description does not explain any parameters. The input schema has a complex nested structure, but the description adds no meaning beyond what the schema provides. Given low schema description coverage, this is a significant gap.

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

Purpose5/5

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

The description clearly states the action (audit), the resource (HUMMBL model references), and the scope (existence, transformation alignment, duplicates). It is specific and distinguishes from sibling tools like get_model or list_all_models.

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

Usage Guidelines3/5

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

The description implies usage when one has a list of model references to check, but it does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives.

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

Deploy Server