Skip to main content
Glama
Sign In

blablabla

by com.sayblablabla
OverviewDiscussionsAdmin

Find practice monologues

list_practice_monologues
Read-only

Use this when an actor wants a solo monologue for reading, memorization, a cold read or selftape practice. Returns published original and public-domain pieces in the requested script language with one role, genre, age range, difficulty, estimated speaking duration, author and each piece's license. Use get_practice_monologue with the same locale to read a chosen piece. An empty list means no piece matches; never invent or cut text to meet a limit. Do not use for two-person scenes, private audition sides, unlisted play excerpts, automatic translation or casting judgments. Rights information applies only to the identified text or edition. This reading-only tool does not offer a verified native opening link or a live voice reader inside this chat.

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_monologues"
  }
}

Input Schema

NameRequiredDescriptionDefault
genreNoRequested genre: comedy or drama. Omit if the actor has no preference.
localeNoScript language. Pass the explicit requested language, otherwise the conversation language; carry the same locale from listing to reading and setup. English is a legacy default only when omitted. Unpublished translations return an error, never English substitution.en
age_rangeNoRequested authored playing-age category: teen, adult or child. This filters material; it does not assess the actor's casting suitability.
difficultyNoRequested practice difficulty: beginner, intermediate or advanced.
max_duration_secondsNoMaximum estimated speaking duration in seconds, for example 120 for a piece up to two minutes. No automatic shortening; an exact limit may return no matches.

Output Schema

NameRequiredDescriptionDefault
kindYes
localeYes
licenseNo
capabilityYes
monologuesYes
catalog_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / age_range / description
      Previous value: -"Requested authored playing-age category: teen or adult. This filters material; it does not assess the actor's casting suitability."New value: +"Requested authored playing-age category: teen, adult or child. This filters material; it does not assess the actor's casting suitability."
    • changedInput schema / properties / age_range / enum
      Previous value: -[
-  "teen",
-  "adult"
-]New value: +[
+  "teen",
+  "adult",
+  "child"
+]
    • addedOutput schema / properties / monologues / items / properties / author
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / monologues / 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 / monologues / items / required
      Previous value: -[
-  "slug",
-  "title",
-  "logline",
-  "genre",
-  "tones",
-  "age_range",
-  "casting_range",
-  "duration_seconds",
-  "difficulty",
-  "content_notes",
-  "role_count",
-  "role_name",
-  "web_url"
-]New value: +[
+  "slug",
+  "title",
+  "logline",
+  "genre",
+  "tones",
+  "age_range",
+  "casting_range",
+  "duration_seconds",
+  "difficulty",
+  "content_notes",
+  "role_count",
+  "role_name",
+  "author",
+  "license",
+  "web_url"
+]
    • changedOutput schema / required
      Previous value: -[
-  "kind",
-  "locale",
-  "capability",
-  "catalog_version",
-  "license",
-  "monologues"
-]New value: +[
+  "kind",
+  "locale",
+  "capability",
+  "catalog_version",
+  "monologues"
+]
  2. Changed5 schema fields changed
    • removedInput schema / properties / locale / const
      Removed value: -"en"
    • changedInput schema / properties / locale / description
      Previous value: -"Authored script language. These monologues are currently English only; do not request or claim a translated version."New value: +"Script language. Pass the explicit requested language, otherwise the conversation language; carry the same locale from listing to reading and setup. English is a legacy default only when omitted. Unpublished translations return an error, never English substitution."
    • addedInput schema / properties / locale / enum
      Added value: +[
+  "en",
+  "ar",
+  "ca",
+  "cs",
+  "da",
+  "de",
+  "el",
+  "es",
+  "es-mx",
+  "fi",
+  "fr",
+  "fr-ca",
+  "he",
+  "hi",
+  "hr",
+  "hu",
+  "id",
+  "it",
+  "ja",
+  "ko",
+  "ms",
+  "nl",
+  "no",
+  "pl",
+  "pt-br",
+  "pt-pt",
+  "ro",
+  "ru",
+  "sk",
+  "sv",
+  "th",
+  "tr",
+  "uk",
+  "vi",
+  "zh-hans",
+  "zh-hant"
+]
    • removedOutput schema / properties / locale / const
      Removed value: -"en"
    • addedOutput schema / properties / locale / enum
      Added value: +[
+  "en",
+  "ar",
+  "ca",
+  "cs",
+  "da",
+  "de",
+  "el",
+  "es",
+  "es-mx",
+  "fi",
+  "fr",
+  "fr-ca",
+  "he",
+  "hi",
+  "hr",
+  "hu",
+  "id",
+  "it",
+  "ja",
+  "ko",
+  "ms",
+  "nl",
+  "no",
+  "pl",
+  "pt-br",
+  "pt-pt",
+  "ro",
+  "ru",
+  "sk",
+  "sv",
+  "th",
+  "tr",
+  "uk",
+  "vi",
+  "zh-hans",
+  "zh-hant"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only, non-destructive and closed-world behavior, but the description adds important context about licenses, empty-list meaning, not inventing or cutting text, and rights applying only to the identified text or edition. It also discloses reading-only limitations regarding native opening links and live voice readers.

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 definition is front-loaded with the use case and returned fields, then moves to routing, empty-result behavior and constraints. It is dense and mostly earns its length, though the final limitations sentence and multiple exclusion clauses make it longer than a minimal description.

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 five optional filters, full schema coverage, annotations and an output schema, the description covers enough for correct selection and invocation: use cases, return fields, follow-up tool, empty-list semantics, exclusions and rights limitations. Nothing critical for calling the tool 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%, so the schema already documents the filters, enums, locale default and translation error behavior. The description reinforces using the requested script language and carrying locale into reading, but adds little parameter meaning beyond what the schema provides, so the baseline 3 is appropriate.

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?

States the specific verb and resource ('list practice monologues') and specifies solo pieces for reading, memorization, cold read or selftape practice. It clearly distinguishes this listing tool from get_practice_monologue and from scene-oriented siblings.

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?

Explicitly says when to use it (actor wants a solo monologue for practice), names the follow-up alternative (get_practice_monologue with the same locale), and lists exclusions such as two-person scenes, private audition sides, unlisted excerpts, automatic translation and casting judgments.

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