Skip to main content
Glama

OODS Foundry

by com.oods-foundry
OverviewDiscussionsAdmin

Look Up Recorded Screen

design_preview
Read-onlyIdempotent

Look up a recorded screen by object, context and framework. Returns its running screen URL, content hash, brand and theme. No new screen is generated. object_registry reads the definition behind the screen. Set reproduce true when the command and calls used to generate it are requested.

Input Schema

NameRequiredDescriptionDefault
objectYesAn object with recorded screens at this version.
contextNoThe context the screen was composed for.detail
frameworkNoThe framework of the generated app.react
reproduceNoInclude the command and calls for reproducing this result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / reproduce
      Added value: +{
+  "default": false,
+  "description": "Include the command and calls for reproducing this result.",
+  "type": "boolean"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / context / description
      Added value: +"The context the screen was composed for."
    • addedInput schema / properties / framework / description
      Added value: +"The framework of the generated app."
    • addedInput schema / properties / object / description
      Added value: +"An object with recorded screens at this version."
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety and idempotency profile is covered. The description adds that no new screen is generated and that object_registry reads the underlying definition, which is useful context, but it does not elaborate on caching, rate limits, or output format beyond naming returned fields.

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 three sentences, front-loaded with the core action and return values, then a scoping clarification and a sibling reference. It is efficient and each sentence contributes, though it could be slightly tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 100% schema coverage and annotations covering safety, the description is adequate for a read-only lookup. It names the returned fields and clarifies that no generation occurs, but lacks details on pagination, error cases, or output structure, which is acceptable given no output schema but leaves some gaps.

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 three parameters have enums, so the schema fully documents parameter meanings and allowed values. The description only adds a conditional note about the 'reproduce' flag, which is already described in the schema; no additional syntax or format details are provided, so baseline 3 applies.

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 states a specific verb and resource ('Look up a recorded screen') and clarifies scope with 'No new screen is generated', distinguishing it from any generation tool. It also names a relevant sibling (object_registry) and contrasts its role, which aids differentiation.

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?

The description implies usage by describing return values and a conditional flag ('Set reproduce true when the command and calls used to generate it are requested'), but it does not explicitly state when to use this tool versus alternatives like object_registry or other siblings. Guidance is implied rather than directive.

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

All OODS Foundry toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources