Skip to main content
Glama
sunshinerich

grafana-log-mcp

by sunshinerich

inspect_fields

Detect missing or default field values by computing null rates and identifying logs with fallback patterns.

Instructions

字段取值与空值探测("变量没设置"时的首选):统计字段空值率、命中"使用默认值/未配置/fallback"的日志样本。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNo
rangeNo默认 1h
startNo
fieldsNo只检查指定字段;不传则自动发现
labelsNo
keywordNo
projectNo
datasourceUidNo
Behavior3/5

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

未提供任何注解,因此描述必须自行承担行为透明度。描述将其描述为只读分析(统计和匹配),但未描述返回结构、样本数量、时间范围或多租户行为。这是一个基础操作,描述并未透露性能或权限方面的细节,尽管该工具看似无害。没有矛盾,但缺乏深度。

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?

描述紧凑且信息丰富,仅用一句话就传达核心功能和使用场景。没有冗余或废话,在简洁性方面是典范。

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?

该工具的参数较多(8个),且没有输出模式,但描述未提供返回值细节(无论是聚合计数还是样本列表)或其他调用约束。描述很简短,未涵盖在昂贵数据集上运行分析所需的深入信息。对于不熟悉该工具的人来说,缺乏重要上下文,得分较低。

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?

输入模式覆盖率为 25%,虽然描述涵盖了“fields”参数(即检查哪些字段),但未解释其他参数(例如 start、end、labels、project)。描述确实为 fields 增加了价值(自动发现与指定,以及链接到变量未设置场景),但其他七个参数的语义仍不明确。考虑到模式覆盖率高,该描述充其量只是部分有用。

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?

描述以清晰的动词“统计”开头,并指定了范围:字段空值率和针对“默认/未配置/回退”日志样本。它明确提到“变量未设置”场景作为首选,将其与查询日志等通用工具区分开来。目的具体且可操作。

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

该描述表明它是“变量未设置”时的首选工具,为使用提供了明确背景。但它没有明确排除其他场景或提及替代方案,如 query_logs 或 diagnose_issue。上下文清晰,但缺乏何时不使用或选择其他工具的说明。

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/sunshinerich/grafana-log-mcp'

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