Skip to main content
Glama

图表读数

analyze_data_visualization

Extract data and insights such as trends, anomalies, and numerical values from charts and dashboards by providing an image, optional questions, and detail level.

Instructions

读懂图表/仪表盘并抽取数据与洞察(趋势、异常、数值)。需要从图表里读出数字或结论时使用。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYes图片:本地路径 / file:// / http(s):// / data: URI
questionNo具体问题或额外要求
detail_levelNo细节级别:overview=单次快速;normal/fine/auto 触发由粗到细的自动缩放(auto 为默认,足够清晰则早退)
regionNo可选:手动指定关注区域,命名如 'top-right' 或归一化 bbox 'x,y,w,h'(0~1)
thinkingNo是否开启视觉模型深度推理(默认按工具/后端策略)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
markdownYes人类可读的结构化 markdown 正文(与 content 一致)
confidenceNo模型对结果的置信度
roundsYes实际经历的视觉调用轮数
regionsNo缩放走过的区域轨迹(归一化 bbox)
warningsYes降级/截断/不确定等告警
providerYes
modelYes
Behavior2/5

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

No annotations provided, so description must cover behavior. It does not mention that it is a read-only operation, authentication needs, rate limits, or that it uses a vision model. Minimal behavioral disclosure.

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?

Two concise sentences front-loaded with action and scope, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers core purpose but omits context like supported chart types or performance notes. Adequate for a tool with output schema.

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 coverage is 100%, so description adds no extra parameter meaning. Baseline 3 is appropriate.

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?

The description clearly states the tool reads charts/dashboards to extract data and insights (trends, anomalies, values), distinguishing it from siblings like general image analysis or text extraction.

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?

Explicitly states when to use (read numbers or conclusions from a chart). Lacks explicit when-not-to-use or alternative tools, but context is clear.

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/Pelican0126/vision-mcp'

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