Skip to main content
Glama

Community Viz List

community_viz_list
Read-only

Lists community visualizations registered in a report, the components using each, and their write fingerprints for safe, conflict-checked edits.

Instructions

Community visualizations registered in the report (Manage community visualizations), the components using each, and the fingerprint for writes.

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

Input Schema

NameRequiredDescriptionDefault
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already declares this as a safe read operation. The description adds useful behavioral context by naming the returned contents, including components and a fingerprint used for writes, but it does not discuss pagination, permissions, or how the fingerprint should be handled.

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 definition is a single front-loaded sentence with no redundant explanation. The parenthetical "Manage community visualizations" is slightly awkward but does not materially distract.

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?

An output schema exists, so the description does not need to explain return values in detail, and the tool itself is simple with one optional parameter. However, the missing semantics for report_id and the absence of usage guidance leave meaningful gaps for an agent deciding when and how to call it.

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?

There is one optional report_id parameter with 0% schema description coverage, so the description carries the burden of explaining it. The phrase "in the report" hints at report scoping, but the optional/null default behavior and what happens when report_id is omitted are not explained.

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 identifies the specific resource and scope: community visualizations registered in a report, the components using each, and a fingerprint for writes. That is clear enough to distinguish a list-metadata operation from a generic report call, though it does not explicitly contrast itself with community_viz_register.

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?

There is no explicit when-to-use guidance, no prerequisites, and no point to an alternative such as community_viz_register. The implied usage is discoverable from the resource name, but the description does not help the agent choose between listing and registering.

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