verse-mcp

List your scenes

list_scenes

Read-only

Retrieve scenes owned by your Verse account, newest first, with links, visibility, size, views, and open review comments to review and manage 3D content.

Instructions

List the scenes owned by your Verse account, newest first: id, link, visibility, size, views and open review comments. Needs VERSE_API_KEY set to your account token.

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_scenes"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of scenes to return.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: the required VERSE_API_KEY credential and the fixed newest-first ordering, which the agent could not infer from annotations alone. It does not state whether results are truncated or paginated, which keeps 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the scope and ordering front-loaded before the returned fields and the credential requirement. Nothing is repeated from the title or schema.

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 usefully enumerates the returned fields and the auth requirement, which is enough for a simple one-parameter list tool. The only gap is truncation/pagination semantics when the scene count exceeds the limit.

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

Parameters3/5

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

There is a single optional parameter (limit) and schema coverage is 100%, so the schema already documents its type, default, and bounds. The description adds nothing about limit behavior, such as what happens when the account has more scenes than the limit, so baseline 3 applies.

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 and resource ('List the scenes'), narrows scope ('owned by your Verse account'), specifies ordering ('newest first'), and enumerates the returned fields. An agent can distinguish this from list_camera_paths or get_scene_status without opening any schema.

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?

Usage is only implied: the account-ownership scope hints at 'list my scenes,' but there is no explicit when-to-use guidance, no mention of alternatives such as list_camera_paths for path-level data, and no exclusions or prerequisites framing beyond the API key note.

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

Deploy Server