Studio Bridge

Official

by Spicy-API

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Check a Studio request

studio_get_request

Read-onlyIdempotent

Retrieve a shared request by ID to resume your in-progress draft and check cancellation state. If missing, treat it as expired or disconnected; do not recreate automatically.

Instructions

Read an existing shared request by its known ID, including cancellation state. Use this to resume your own in-progress draft. Missing requests expired or were disconnected; do not recreate them automatically.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "studio_get_request"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Sep 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely non-structured context: the response includes cancellation state, and a missing request means it expired or was disconnected. That interpretive guidance is what an agent can't derive from annotations.

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?

Three short sentences, front-loaded with the action, then usage, then the failure-mode caveat. No filler; every clause carries information.

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?

With an output schema present, return values need no explanation, and annotations cover safety. The description still adds the one thing an agent would otherwise get wrong — treating a missing request as an error to retry rather than an expired resource.

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?

Only one parameter, with 0% schema description coverage, so the description must carry the load. 'Known ID' usefully implies the ID must be obtained beforehand rather than guessed, but no format or sourcing detail is added. Adequate but thin for a zero-coverage schema.

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?

States a specific verb and resource ('Read an existing shared request by its known ID') plus an extra scope detail (cancellation state). It hints at its niche ('resume your own in-progress draft') but does not explicitly contrast itself with siblings like studio_next_request or studio_connect.

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 a clear when-to-use ('resume your own in-progress draft') and a caution against misuse ('do not recreate them automatically'). However, it never names an alternative tool or the condition that selects a sibling over this one.

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

Deploy Server