Skip to main content
Glama

review_image_structure

Read-only

Review image-reconstruction trace specs to list card groupings, duplicate structures, text hierarchy, shared styles, and non-editable or proofreading content as source-linked candidates.

Instructions

只读审阅图片重建的 trace spec:列出卡片分组、重复结构、文字层级、共享样式及不可编辑图片/待校对文案。结果是带源码指针的候选,不推测交互或自动改层级。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "spec": "<spec>"
    },
    "name": "review_image_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the description's 'read-only' is partly redundant; the value it adds is beyond that — the output is explicitly 'candidates with source pointers' and the tool will not rewrite hierarchy or speculate about interactions. That non-mutation and output-character disclosure is exactly the extra context annotations cannot express.

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 tight sentences: the read-only review scope leads, then the enumerated findings, then the caveats about candidate-only output. No filler, and the most important constraint is front-loaded.

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?

With no output schema, the description does a reasonable job sketching what comes back (candidates plus source pointers). But for a 2-parameter tool with 0% schema coverage, leaving `limit` and the string-vs-object `spec` form entirely undocumented is a real gap in an otherwise complete picture.

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%, so the description must compensate and it largely does not. It references 'trace spec' (the required `spec` param accepts either string or object) but gives no hint about the accepted shape or format, and the `limit` parameter (1-100) is never mentioned at all.

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 names a specific verb and resource: read-only review of an image-reconstruction 'trace spec'. It also enumerates what gets surfaced (card groupings, repeated structures, text hierarchy, shared styles, non-editable images, copy awaiting proofreading), which lets an agent picture the output. It stops short of naming which sibling performs generation (e.g. generate_from_image), so sibling differentiation is only implicit.

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?

The word 'only-read review' plus the exclusions 'does not infer interactions or auto-change hierarchy' imply the conditions for calling it (post-reconstruction inspection rather than generation). However, there is no explicit when-to-use statement and no named alternative for the generation step, so an agent must infer routing from the exclusion list.

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