Skip to main content
Glama
Sign In
Kranz MCP

Kranz MCP

by kranz-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

action_list

List actions in a Kranz runtime, optionally filtered by exact owner, to review lifecycle operations available for local development services.

Instructions

List actions, optionally filtered by exact owner.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "action_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerNo
runtimeNoProject runtime to address, by name or id from runtimes. Omit to use the project this MCP server was started in.

Output Schema

NameRequiredDescriptionDefault
dataNoTool-specific payload; absent on failure.
errorNoCausal failure, absent on success.
sessionNoThe runtime that served this call; absent for global tools and for failures that resolved no runtime.
generationNoConfiguration generation the answer was read at; absent when no runtime served the call.
schema_versionYesEnvelope contract version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.17.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses almost nothing beyond the verb. Read-only semantics are only implied by 'List'; scope (project-scoped via the server's starting project), pagination, and result ordering/limits are unstated.

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?

One short sentence, front-loaded with the action and qualified by the filter. Nothing redundant and nothing 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?

An output schema exists, so return values need not be described, and the runtime parameter's scope is covered in-schema. However, with no annotations and a terse description, the agent gets no statement of read-only safety, project scoping defaults, or result volume limits.

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 50%: the 'runtime' parameter is documented in the schema, while 'owner' is bare. The description compensates for 'owner' by stating it filters by exact match and is optional, but adds nothing about runtime scoping or matching syntax beyond what the schema already says.

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+resource ('List actions') and the optional filter dimension ('exact owner'), so the agent knows this is the read/discovery tool. It does not explicitly differentiate itself from siblings like action_info, action_run, or action_result, though the list-vs-single/exec verbs make the distinction reasonably inferable.

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 phrase 'optionally filtered by exact owner' implies usage (use when you want a broad listing or a per-owner subset) but never states when to prefer this over action_info or action_result. Usage is implied rather than guided.

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