Skip to main content
Glama
smeet666

mcp-stashbox

Read one scene

get_scene
Read-onlyIdempotent

Retrieve a scene's full details using its identifier from the stash-box catalogue. Optionally load fingerprints or images sections.

Instructions

Read one catalogued scene by its identifier. The identifier names the catalogue that minted it, as returned by search_scenes or find_by_fingerprint. Sections are opt-in because a scene's fingerprints weigh more than everything else it carries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesIdentifier as returned by another tool, such as stashdb:<uuid>.
sectionsNoWhich blocks to load. Defaults to basic.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
codeNoThe studio's own reference, in whatever form it publishes.
tagsNo
urlsNo
notesYes
titleNo
imagesNo
sourceYes
statusYes'established' is a record the catalogue holds. 'merged' and 'deleted' are markers: the identifier resolves, and what comes back describes the record rather than the thing it once named.
studioNo
createdNo
detailsNo
updatedNo
directorNoFree text, which can name several people.
performersNo
source_urlYes
merged_intoNoPresent on a marker: the identifier that continues this record.
fingerprintsNo
former_titleNoPresent on a marker: the title the record carried.
release_dateNoWhen the scene was published.
retrieved_atYesWhen this record came off the catalogue, ISO 8601.
production_dateNoWhen the scene was made, which is a different question from when it was published. Rarely recorded, and never filled in from the release date.
duration_secondsNo
fingerprint_countNo
fingerprints_heldNoHow many the record holds, where the section shows a page of them.
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond annotations: sections are opt-in because fingerprints are heavy, and the identifier names the catalogue. No contradictions.

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, front-loaded with the core purpose, then a compact explanation of identifier provenance and sections rationale. No wasted words.

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 simple read tool with full schema coverage, output schema, and strong annotations, the description covers the essential aspects: identifier source, default sections, and performance reasoning. Nothing critical is missing.

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 good parameter descriptions. The description adds minor context (e.g., 'catalogue that minted it', 'fingerprints weigh more') but mostly reiterates what the schema already states.

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 uses a specific verb ('Read') with a clear resource ('one catalogued scene') and identifier-based access. It distinguishes from siblings by specifying a single scene lookup as opposed to search tools like search_scenes or find_by_fingerprint.

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?

It clearly implies usage after obtaining an identifier from search_scenes or find_by_fingerprint, giving the sequence of tool usage. It does not explicitly state when not to use it or contrast with get_performer, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smeet666/mcp-stashbox'

If you have feedback or need assistance with the MCP directory API, please join our Discord server