Skip to main content
Glama
Sign In
Spring Toolkit MCP

Spring Toolkit MCP

by giaffa86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_log_file

Reads the Spring Boot actuator logfile as bounded text, requiring actuator downloads to be enabled.

Instructions

Read /actuator/logfile as bounded text when actuator downloads are enabled.

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": "get_log_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_charsNo
applicationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden. It mentions 'bounded text' implying truncation, but fails to disclose whether the operation is read-only, requires authentication, or what happens if actuator downloads are disabled.

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?

Single sentence with no unnecessary words. Efficiently conveys the core purpose and a key condition.

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?

Despite the tool's simplicity (2 optional params, no output schema), the description omits essential details: what the bounded text format is, how max_chars affects output, the role of application parameter, and error conditions. Incomplete for an agent to use reliably.

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 description coverage is 0%, and the description does not explain the purpose or behavior of either parameter (max_chars or application). The parameter names hint at meaning, but the description adds no value 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 clearly states the action (Read) and resource (/actuator/logfile) and includes the condition 'when actuator downloads are enabled'. It is specific enough to distinguish from sibling actuator tools like get_info or list_actuator_endpoints.

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?

No guidance on when to use this tool versus alternatives. It only mentions a precondition ('when actuator downloads are enabled') but does not explain when not to use it or suggest other tools for similar purposes.

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