Skip to main content
Glama

查参数、输出位置与展示规范

info

Provides parameter lookup, output path rules, Markdown display templates, and connectivity status so you can verify image-generation setup before submitting jobs.

Instructions

返回参数速查、输出位置规则、Markdown 展示规范与模板、当前配置与连通性。 不确定参数怎么传、图片要放哪、多张图怎么排才不被渲染破坏,先调这个。

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": "info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does reasonably well: it states the tool returns current configuration and connectivity, signalling a read/probe operation that may touch live state. It never explicitly declares the tool read-only or side-effect free, leaving a small ambiguity about the connectivity check.

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?

Two dense sentences: the first enumerates returned content, the second gives usage triggers, so the reader gets capabilities before the call-to-action. The enumeration is list-like but every clause maps to a real output area, so little is wasted.

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?

A zero-param, no-annotation, no-output-schema tool needs the description to enumerate its return contents, and it does exactly that across five areas. The only residual gap is that it does not say how the result is formatted or how large it is, a minor omission for a help tool.

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 tool takes zero parameters and the schema is fully empty with 100% coverage, so the baseline is 4. Nothing in the description needs to compensate, and it correctly implies the call is argument-free by presenting it as a lookup to run before configuring anything.

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 set of resources returned (parameter cheatsheet, output-location rules, Markdown display conventions/templates, current config, connectivity), which rescues the otherwise vague name 'info'. It is clear what the tool delivers, though it never distinguishes itself from the sibling create_images beyond the implicit help-desk role.

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?

The second sentence gives concrete triggering conditions (unsure how to pass params, where to place images, how to lay out multiple images without breaking rendering) and an explicit 'call this first' instruction. It stops short of any when-not-to-use exclusion, which keeps it at 4 rather than 5.

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