Skip to main content
Glama
Sign In

blablabla

by com.sayblablabla
OverviewDiscussionsAdmin

Find two-person practice scenes

list_practice_scenes
Read-only

Use this when an actor needs a published two-person script for scene practice, cold reading, line memorization or selftape preparation, including when they have no scene partner. Returns app-published scenes and roles in the requested language, with each piece's author and license. Read a chosen scene with get_practice_scene before offering its app link. Do not use to find private audition sides, monologues or an organization's repertoire; this tool does not provide a live reader inside this chat. In the blablabla app, the other part is read aloud.

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

Input Schema

NameRequiredDescriptionDefault
localeNoScript language, for example en or da. Pass the explicitly requested script language, otherwise the conversation language. Carry the same locale through listing, reading and setup. English is a legacy default only when omitted. Unpublished versions return an error, never a translation.en

Output Schema

NameRequiredDescriptionDefault
localeYes
scenesYes
licenseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / scenes / items / properties / author
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / scenes / items / properties / license
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "name": {
+      "type": "string"
+    },
+    "permittedUses": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "restrictions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "status": {
+      "const": "published",
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "summary",
+    "permittedUses",
+    "restrictions",
+    "status"
+  ],
+  "type": "object"
+}
    • changedOutput schema / properties / scenes / items / required
      Previous value: -[
-  "slug",
-  "title",
-  "logline",
-  "genre",
-  "duration_minutes",
-  "characters",
-  "open_url",
-  "web_url"
-]New value: +[
+  "slug",
+  "title",
+  "logline",
+  "genre",
+  "duration_minutes",
+  "characters",
+  "author",
+  "license",
+  "open_url",
+  "web_url"
+]
    • changedOutput schema / required
      Previous value: -[
-  "locale",
-  "license",
-  "scenes"
-]New value: +[
+  "locale",
+  "scenes"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / locale / description
      Previous value: -"Script language, for example en or da. Defaults to English; unsupported publication returns an explicit error, never an automatic translation."New value: +"Script language, for example en or da. Pass the explicitly requested script language, otherwise the conversation language. Carry the same locale through listing, reading and setup. English is a legacy default only when omitted. Unpublished versions return an error, never a translation."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/non-destructive/openWorld annotations, the description adds return content (app-published scenes and roles with each piece's author and license), availability constraints (only app-published material), and a key expectation-setting note that no live reader exists inside the chat while the app reads the other part aloud. Minor duplication of the schema's 'unpublished versions return an error' caveat keeps it from a 5.

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 when-to-use condition is front-loaded and every sentence carries information (return contents, sequencing, exclusions, app behavior), though the opening sentence is long and heavily clause-stacked.

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 one-parameter, read-only listing tool with annotations and an output schema, the description covers the trigger, the return shape, the sequencing to the sibling reader tool, the exclusions, and the in-app reading behavior — nothing an agent needs to select or call it 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?

With a single parameter and 100% schema coverage including a 36-value enum and detailed locale guidance, the schema does the heavy lifting. The description only restates that results come back 'in the requested language', adding no new semantics about the locale parameter.

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 states a specific resource (published two-person practice scenes with roles) and the concrete user situation (an actor with no scene partner preparing for cold reading, line memorization or selftape), which lets an agent separate it from list_practice_monologues without opening either schema.

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?

It gives an explicit trigger ('when an actor needs a published two-person script'), explicit exclusions ('private audition sides, monologues or an organization's repertoire'), and an explicit follow-up path ('Read a chosen scene with get_practice_scene before offering its app link').

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

All blablabla toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources