Skip to main content
Glama

ScanBIM MCP

by io.scanbimlabs
OverviewDiscussionsAdmin

xr_list_sessions

List the last 20 VR/AR sessions launched via xr_launch_vr_session and xr_launch_ar_session, sorted by creation time desc. Sourced from the D1 usage_log table; returns an empty array if D1 is unavailable or no sessions have been recorded. When to use: you want to audit who launched which XR session and when, or surface recent sessions to a user. When NOT to use: you want details (join URL, features) for a specific session — those details live inside the original launch response and are not stored beyond the log row. APS scopes: none (D1 read only). Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable. Errors: 401 APS token expired/invalid — refresh (not applicable: no APS call); 403 scope or resource permission denied (not applicable); 404 not applicable; 429 rate limited — backoff and retry (worker-level only); 5xx APS upstream outage — retry with jitter (not applicable). Side effects: READ-ONLY. Idempotent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
model_idNoReserved for future filtering by model URN. Currently not applied; all recent xr_* sessions are returned.
session_typeNoReserved for future filtering by session type. Currently not applied; both VR and AR sessions are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / model_id / description
      Added value: +"Reserved for future filtering by model URN. Currently not applied; all recent xr_* sessions are returned."
    • addedInput schema / properties / model_id / examples
      Added value: +[
+  "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1tb2RlbHMvMTcwMDAwMDAwMDAwMF9idWlsZGluZy5ydnQ"
+]
    • addedInput schema / properties / session_type / description
      Added value: +"Reserved for future filtering by session type. Currently not applied; both VR and AR sessions are returned."
    • addedInput schema / properties / session_type / examples
      Added value: +[
+  "all"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries full burden. It discloses read-only/idempotent behavior, D1 data source, empty array fallback, rate limits, error responses, and side effects. This is exceptional coverage for a simple list tool.

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 description is well-structured with clear labeled sections and front-loaded purpose. However, it includes irrelevant rate limit information (Model Derivative, OSS uploads) and 'not applicable' error entries that add noise and do not pertain to this tool.

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?

Given no output schema and no annotations, the description is unusually complete. It covers use cases, exclusions, data source, ordering, empty-array behavior, auth requirements, rate limits, error handling, and side effects, making the tool self-contained for an agent.

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%, with both parameters described as 'reserved' and 'currently not applied.' The tool description adds no additional parameter-level detail beyond the schema, so the 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?

The description opens with a specific verb ('List'), resource ('last 20 VR/AR sessions'), source ('launched via xr_launch_vr_session and xr_launch_ar_session'), and ordering ('creation time desc'). It clearly distinguishes from sibling launch tools and other list tools like acc_list_issues.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'When to use' and 'When NOT to use' sections, including what details are not available (join URL, features) and where they live. Names alternatives indirectly by referencing the original launch response, giving clear decision criteria.

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

All ScanBIM MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources