Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_workspace_get

Fetches an office's declarative workspace spec and last preparation result by flow ID, so you can inspect its environment definition and setup outcome.

Instructions

Show an office's declarative workspace spec and how its last preparation went.

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": {
      "flow_id": "<flow_id>"
    },
    "name": "kernel_agents_workspace_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
flow_idYesOffice (flow) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the transparency burden. "Show" implies a read-only inspection and it names the returned artifacts, but it does not explicitly confirm absence of side effects, permissions needed, or behavior when no preparation has run.

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 definition is a single front-loaded sentence with no wasted wording. It efficiently states what is retrieved and what result context is included.

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 a simple one-parameter retrieval tool, the description adequately identifies the returned spec and preparation outcome. However, "how its last preparation went" remains vague, and with no output schema the description could say more about the returned status information.

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

Parameters3/5

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

Schema coverage is 100%, so the single flow_id parameter is already fully documented. The description only implicitly maps "office" to that parameter and adds no format or semantic detail beyond the schema.

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 gives a specific retrieval verb ("Show") and identifies two concrete resources: an office's declarative workspace spec and its last preparation result. It is clear what the tool returns, but it does not explicitly differentiate itself from the sibling kernel_agents_workspace_apply.

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 explicit guidance on when to call this versus workspace_apply, nor any stated prerequisites or exclusions. The inspection use case is only weakly implied by the word "Show".

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