Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_panel_record_put

Create or replace one record in an office panel collection using a stable key, keeping operator-visible issue or event data current.

Instructions

Create or replace one record in a collection of YOUR office's panel (shown to the operator in the office panel). Use a stable key (e.g. the issue key).

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": {
      "collection": "<collection>",
      "key": "<key>",
      "data": "<data>"
    },
    "name": "kernel_panel_record_put"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
dataYes
collectionYesCollection name declared in your office's panels (e.g. events)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the most important behavioral trait — that a record with the same key is replaced rather than duplicated — but says nothing about permissions, what happens with an undeclared collection, or what a failed/overwritten write returns.

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?

Two short sentences, front-loaded with the action and followed by the key guidance; the parenthetical about the operator panel is slightly redundant but clarifies audience. Nothing is padded.

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?

For an unannotated mutation tool with a nested object parameter and no output schema, the description covers the critical overwrite semantics and key strategy but omits the shape/semantics of 'data' and any error or return behavior. Adequate to call safely only if the agent already knows the panel record format.

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 coverage is only 33% (only 'collection' is described in the schema), so the description must compensate. It adds real meaning for 'key' ('a stable key, e.g. the issue key') but leaves 'data' — a nested object-of-objects with additionalProperties — entirely unexplained, including what a single record's payload should look like.

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: 'Create or replace one record in a collection of YOUR office's panel.' The create-or-replace framing implicitly distinguishes it from the sibling kernel_panel_record_append, but the sibling is never named, so an agent must infer the difference.

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?

Usage context is implied ('YOUR office's panel', 'shown to the operator') and the key-selection advice ('Use a stable key') is actionable, but there is no explicit statement of when to choose this over kernel_panel_record_append, nor of prerequisites such as the collection needing to be declared.

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

Deploy Server

Other Tools