Skip to main content
Glama
Sign In
go2rtc-mcp

go2rtc-mcp

by gaxkalik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_server_logs

Fetch recent go2rtc server logs with sensitive data redacted to diagnose camera streaming issues and monitor system health.

Instructions

Retrieve the most recent limit log entries from go2rtc (GET /api/log), sanitized.

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_server_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that output is 'sanitized' (secrets redacted) and that entries are the most recent ones, but says nothing about permissions, retention, ordering guarantees, or volume limits.

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 front-loaded sentence with the action, scope, source, and the sanitization caveat; every clause earns its place.

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 single-parameter read tool with an output schema covering return values, the description supplies the essential semantics. Only behavioral details (auth, retention, ordering) are absent.

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

Parameters4/5

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

The single parameter is undocumented in the schema (0% coverage), but the description compensates by explaining that `limit` controls how many of the most recent log entries are returned. It does not mention bounds or the default of 50, which is left to 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?

Specific verb (retrieve) plus resource (log entries) and source endpoint (GET /api/log from go2rtc), so it is clearly distinguishable from get_server_info or get_config. It does not explicitly name siblings, but the resource noun is unambiguous.

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 statement of when to use this versus alternatives such as get_server_info or get_config, and no preconditions or exclusions. Usage is only inferable from the purpose.

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