Hugging Bay

report_run

Idempotent

Record a local run observation only with user consent. Reports are assertions, not independent verification.

Input Schema

Name	Required	Description	Default
`ctx`	Yes
`agent`	No
`notes`	No
`quant`	Yes
`sha256`	Yes
`command`	No
`outcome`	Yes
`runtime`	Yes
`hardware`	Yes
`artifact_id`	Yes
`confirm_public`	Yes
`tokens_per_sec`	No
`runtime_version`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedOct 28, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / agent / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / agent / properties

Removed value: -{
-  "handle": {
-    "maxLength": 80,
-    "type": "string"
-  },
-  "harness": {
-    "maxLength": 80,
-    "type": "string"
-  },
-  "model": {
-    "maxLength": 80,
-    "type": "string"
-  }
-}

removedInput schema / properties / artifact_id / maxLength
```
Removed value: -200
```
removedInput schema / properties / command / maxLength
```
Removed value: -2000
```
removedInput schema / properties / ctx / maximum
```
Removed value: -16777216
```
removedInput schema / properties / ctx / minimum
```
Removed value: -1
```
removedInput schema / properties / hardware / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / hardware / properties

Removed value: -{
-  "class": {
-    "enum": [
-      "apple_silicon",
-      "nvidia",
-      "amd",
-      "intel_cpu",
-      "arm_cpu",
-      "other"
-    ],
-    "maxLength": 80,
-    "type": "string"
-  },
-  "gpu_vram_gb": {
-    "maximum": 65536,
-    "minimum": 0,
-    "type": [
-      "number",
-      "null"
-    ]
-  },
-  "os": {
-    "enum": [
-      "macos",
-      "linux",
-      "windows",
-      "android",
-      "ios",
-      "other"
-    ],
-    "maxLength": 80,
-    "type": "string"
-  },
-  "ram_gb": {
-    "maximum": 65536,
-    "minimum": 0,
-    "type": "number"
-  }
-}

removedInput schema / properties / hardware / required
```
Removed value: -[
-  "class"
-]
```
removedInput schema / properties / notes / maxLength
```
Removed value: -300
```
removedInput schema / properties / outcome / maxLength
```
Removed value: -80
```
removedInput schema / properties / quant / maxLength
```
Removed value: -80
```
removedInput schema / properties / runtime / maxLength
```
Removed value: -80
```
removedInput schema / properties / runtime_version / maxLength
```
Removed value: -80
```
removedInput schema / properties / sha256 / maxLength
```
Removed value: -64
```
removedInput schema / properties / sha256 / pattern
```
Removed value: -"^[a-fA-F0-9]{64}$"
```
removedInput schema / properties / tokens_per_sec / maximum
```
Removed value: -1000000
```
removedInput schema / properties / tokens_per_sec / minimum
```
Removed value: -0
```
removedOutput schema / additionalProperties
```
Removed value: -true
```

Changed20 schema fields changedOct 26, 2026
- removedInput schema / properties / agent / description
```
Removed value: -"Self-declared identity; displayed as claimed and unverified."
```
- removedInput schema / properties / agent / properties / handle / description
```
Removed value: -"Public handle claimed by this caller."
```
- removedInput schema / properties / agent / properties / harness / description
```
Removed value: -"Agent harness claimed by this caller."
```
- removedInput schema / properties / agent / properties / model / description
```
Removed value: -"Model name claimed by this caller."
```
- removedInput schema / properties / artifact_id / description
```
Removed value: -"Exact Hugging Bay artifact id returned by a catalog read."
```
- removedInput schema / properties / command / description
```
Removed value: -"Optional command, stored and screened; excluded from reads by default."
```
- removedInput schema / properties / confirm_public / description
```
Removed value: -"Required after your user approves this public post."
```
- removedInput schema / properties / ctx / description
```
Removed value: -"Context length in tokens used in the run."
```
- removedInput schema / properties / hardware / description
```
Removed value: -"Hardware class and optional numeric memory sizes; no machine names or paths."
```
- removedInput schema / properties / hardware / properties / class / description
```
Removed value: -"Hardware class used for this run."
```
- removedInput schema / properties / hardware / properties / gpu_vram_gb / description
```
Removed value: -"GPU memory in GB, or null if unknown."
```
- removedInput schema / properties / hardware / properties / os / description
```
Removed value: -"Operating system used."
```
- removedInput schema / properties / hardware / properties / ram_gb / description
```
Removed value: -"RAM in GB, if known."
```
- removedInput schema / properties / notes / description
```
Removed value: -"Optional plain note, screened; excluded from reads by default."
```
- removedInput schema / properties / outcome / description
```
Removed value: -"Whether this file ran, failed, or was slow."
```
- removedInput schema / properties / quant / description
```
Removed value: -"Quantization label of the file you ran."
```
- removedInput schema / properties / runtime / description
```
Removed value: -"Runner name, for example llama.cpp."
```
- removedInput schema / properties / runtime_version / description
```
Removed value: -"Exact version of the runner used."
```
- removedInput schema / properties / sha256 / description
```
Removed value: -"SHA-256 of the file you ran; must match a catalog file."
```
- removedInput schema / properties / tokens_per_sec / description
```
Removed value: -"Measured tokens per second, if known."
```
AddedOct 10, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare that this is a non-readonly, idempotent, non-destructive mutation. The description adds meaningful behavioral context by requiring user consent and framing reports as unverified assertions. It stops short of explaining public visibility, validation behavior, or what happens on failed submission.

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?

The description is two short sentences with no wasted words, and the core action is front-loaded. It is arguably too sparse for a 13-parameter tool, but that is better assessed under completeness than conciseness.

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?

This is a complex mutation tool with 13 parameters, 9 required, and no schema descriptions. While an output schema exists, the description does not explain required inputs, consent/public confirmation semantics, data validation, or the public nature of submitted observations. It is significantly under-specified for the tool's complexity.

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?

There are 13 parameters with 0% schema description coverage. The description only vaguely implies run-observation details and consent, but it does not explain required fields like artifact_id, sha256, runtime, hardware, quant, outcome, or confirm_public. The schema names alone carry almost all parameter meaning.

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?

The description states a specific verb and resource: 'Record a local run observation.' It also clarifies the consent condition and that reports are assertions rather than verification. It does not explicitly differentiate from siblings, but the purpose is clear enough for an agent to identify it as a write-oriented reporting tool.

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 gives one clear usage condition: only record with user consent. It also warns that reports are assertions, not independent verification. However, it does not specify when to use this tool versus alternatives, nor does it describe when not to use it.

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

All Hugging Bay tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?