Skip to main content
Glama

List diagrams

list_diagrams
Read-onlyIdempotent

Lists diagrams this connection can access, most recently updated first, each with its permission (read, write or delete: what this connection may do with it, as in list_workspaces; moving it to the trash needs delete). Filters by workspaceId or a title query; pages with cursor (nextCursor) and limit (≤ 50). Node and edge counts are not included (get_canvas outline has them).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoCase-insensitive title search.
cursorNo
workspaceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real behavioral context: results are ordered most-recently-updated-first, each item carries a permission level whose semantics are explained (trash requires delete, referencing list_workspaces), and node/edge counts are deliberately omitted. It does not state total-count or end-of-pagination behavior, keeping it below a 5.

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?

A single dense paragraph that front-loads purpose, then ordering, then item shape, then filtering/paging, then exclusions. Every clause carries information, though the parenthetical asides make it slightly cluttered for one sentence block.

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?

With no output schema, the description does explain what comes back (items with permission, nextCursor paging) and what does not (node/edge counts). It omits total counts and terminal-page signals, but an agent has enough to call and interpret the result correctly.

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?

Schema coverage is only 25% (only `query` is documented in the schema), so the description must compensate, and it largely does: it explains workspaceId as a workspace filter, query as title search, cursor as the nextCursor paging token, and limit as ≤ 50. It does not state defaults (limit default 20) or cursor opacity, leaving a small gap.

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?

States a specific verb (lists) and resource (diagrams), plus the scope ('this connection can access'), sort order ('most recently updated first'), and per-item payload (permission). It also explicitly separates itself from get_canvas for node/edge counts, so an agent can distinguish it from siblings without inspecting schemas.

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?

Gives concrete selection conditions: use workspaceId to filter by workspace, query for title search, cursor/limit for paging, and routes to get_canvas when counts are needed. It lacks an explicit 'do not use for X' beyond that single redirect, but the usage context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.