visio-mcp

Overview Schema Source Related Servers Discussions Admin

List pages

visio_list_pages

Read-only

List pages in a Visio document with their dimensions in inches and shape counts. Specify a file by name or index, or omit to target the active document.

Instructions

List the pages of a document, with their size in inches and shape counts.

Args: document: File name or 1-based index. Omit for the active document.

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

Input Schema

Name	Required	Description	Default
`document`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4.4/5.0

Behavior3/5

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

readOnlyHint=true already communicates the safety profile. The description adds active-document default behavior and what fields are returned, but does not discuss error behavior, pagination, or performance. This is acceptable given the read-only annotation, but not exceptional.

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?

The description is one clear sentence plus an Args block. The purpose is front-loaded and useful details are present with no filler.

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

Completeness5/5

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

For a single-parameter read-only list operation with an output schema, the description is complete. It explains the parameter semantics and the type of information returned, leaving little ambiguity for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description is the only source of semantics for the 'document' parameter. The Args section explicitly describes file name or 1-based index and the active-document default, fully compensating for the schema.

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 a specific action ('List the pages'), the resource (pages of a document), and the return content (size in inches and shape counts). This distinguishes it from siblings like visio_list_documents, visio_list_shapes, and rendering/export tools.

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 description gives practical context by explaining how to specify the document (file name or 1-based index and active document when omitted). It does not explicitly compare with or exclude sibling tools, but the context is clear enough for choosing it to list page information.

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