Skip to main content
Glama
jillesca

gNMIBuddy

by jillesca

get_logs

Retrieve and filter logs from network devices. Specify device name, time range, or keywords to narrow results.

Instructions

Get logs from a network device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
minutesNoNumber of minutes to filter logs (default: 5 minutes). Can be provided as string or integer.
keywordsNoOptional keywords to filter logs
device_nameYesName of the device in the inventory
show_all_logsNoIf True, return all logs without time filtering (default: False)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nosYesSupported Network Operating Systems
dataNo
statusYesEnumeration for network operation status values. Provides type safety and prevents typos when setting or checking operation status in NetworkOperationResult objects.
metadataNo
ip_addressYes
device_nameYes
error_responseNo
operation_typeYes
feature_not_found_responseNo
Behavior2/5

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

No annotations are present, so the description must bear the full burden. It does not disclose any behavioral traits such as being read-only, authentication requirements, or impact on the device.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise and front-loaded. However, it is overly minimal.

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?

Given the tool has 4 parameters and an output schema, the description is too brief. More context about log format or typical usage would improve completeness.

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 description coverage is 100%, so the schema already documents parameters. The description adds no additional meaning beyond what the schema provides, meeting the baseline.

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 ('Get logs') and resource ('network device'). It distinguishes from sibling tools like 'get_routing_info' and 'get_interface_info' by focusing on logs, but does not explicitly differentiate.

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 is provided on when to use this tool versus alternatives. The description lacks context for appropriate usage scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jillesca/gNMIBuddy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server