Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Read the 3D view selection

view_3d_state
Read-only

Retrieves the part a user selected in a 3D viewer plus the camera position at that moment, defaulting to the most recent view when no viewId is given.

Instructions

Return the part the user selected in a view_3d viewer and the camera at that moment, or "nothing selected yet". Without viewId the most recent view is used.

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

Input Schema

NameRequiredDescriptionDefault
viewIdNoviewId from view_3d (default: the latest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds genuinely new context by disclosing the return payload (part plus camera at that moment) and the literal sentinel 'nothing selected yet'. It stops short of saying what happens if no view ever existed versus an empty selection.

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 short sentences, front-loaded with the return value and the sentinel case before the default-behaviour clause. The default clause mildly duplicates the schema, but nothing is wasted overall.

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 read-only, single-optional-parameter tool with no output schema, so the description must convey the return shape — and it does, naming part, camera, and the empty sentinel. Adequate for its complexity; only edge cases around missing views remain unstated.

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?

Schema coverage is 100% and the viewId property already documents 'default: the latest', so the description's fallback sentence mostly restates structured data. No added meaning such as format, provenance, or how to obtain a viewId beyond the schema's note.

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 verb and resource: return the selected part plus the camera pose from a view_3d viewer, and it defines the empty-state string. It implicitly separates itself from view_3d (the viewer itself) but never names a sibling outright.

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 by the read phrasing and the default-behaviour note; there is no explicit 'use this when...' or routing to view_3d_select for making a selection. An agent can infer the read-state purpose, but nothing is stated about prerequisites such as whether a view must already exist.

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