Skip to main content
Glama

server_get_logs

Read-only

Retrieve deduplicated FXServer console log lines and use the returned cursor plus epoch to read only newer entries.

Instructions

Read deduplicated FXServer console lines. Pass the returned next as after (with epoch) to read only newer lines.

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

Input Schema

NameRequiredDescriptionDefault
afterNo
epochNo
levelNo
limitNo
serverNo
resourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that lines are deduplicated and that next/after/epoch enable incremental reads, but it does not discuss permissions, rate limits, or return shape.

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 description is two sentences with no filler, and the core read action is front-loaded before the pagination detail. Every sentence adds useful information.

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?

For a tool with six optional parameters and no output schema, the description is thin. It explains pagination enough to use after/epoch, but it omits filters such as level, limit, server, and resource, and does not describe what the returned log lines look like.

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 description coverage is 0% across six parameters, so the description must carry the load. It clarifies only after and epoch, leaving level, limit, server, and resource undocumented anywhere.

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 states a clear verb and resource: read deduplicated FXServer console lines. It is immediately understandable, but it does not differentiate this tool from the sibling client_get_logs or explain what is server-specific versus client-specific.

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?

It gives useful incremental-read guidance by explaining that the returned next should be passed as after with epoch to fetch only newer lines. However, it does not say when to choose this tool over client_get_logs or server_get_diagnostics, nor does it describe exclusions or alternatives.

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