Skip to main content
Glama
Sign In
krexel-mcp

krexel-mcp

by Syfer-web
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_logs

Retrieve build logs for a deploy to troubleshoot deployment issues. Provide a deploy ID to access relevant log data.

Instructions

Get build logs for a deploy. In Phase 1 these are mocked from the local manifest; Phase 2 will stream from the orchestrator.

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": {
      "deploy_id": "<deploy_id>"
    },
    "name": "get_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
deploy_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries full burden; it discloses that logs are currently mocked from the local manifest and will stream in Phase 2, which is useful transparency beyond a simple 'get logs'.

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?

Two sentences, front-loaded with the core function, no wasted words. Every sentence adds value.

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

Completeness4/5

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

For a simple tool with one parameter and no output schema, the description covers the purpose and current behavior (mocked logs). Slightly better than minimal due to the phase context.

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?

Schema coverage is 0%, and the description does not explain the deploy_id parameter beyond what the schema provides (type and pattern). The description must compensate but does not.

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 verb 'Get' and the resource 'build logs for a deploy', distinguishing it from sibling tools like get_status or list_deploys.

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 context by mentioning Phase 1 and Phase 2, but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria.

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