Skip to main content
Glama

Shakespeare's Monologues

by io.github.slshults
OverviewDiscussionsAdmin

get_scene_summary

Fetch an AI-generated summary of the scene a monologue appears in (context for the speech). May be null if not generated yet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe monologue's numeric id (from search_monologues).
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
monologue_idNoDeprecated alias for `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The numeric id of a monologue in the scene."New value: +"The monologue's numeric id (from search_monologues)."
    • addedInput schema / properties / monologue_id
      Added value: +{
+  "description": "Deprecated alias for `id`.",
+  "type": "integer"
+}
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "context"
-]New value: +[
+  "context"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
+  "description": "The numeric id of a monologue in the scene.",
+  "type": "integer"
+}
    • removedInput schema / properties / monologue_id
      Removed value: -{
-  "description": "The id of a monologue in the scene.",
-  "type": "integer"
-}
    • changedInput schema / required
      Previous value: -[
-  "monologue_id",
-  "context"
-]New value: +[
+  "id",
+  "context"
+]
  3. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "monologue_id"
-]New value: +[
+  "monologue_id",
+  "context"
+]
  4. First observed

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden. It discloses the possibility of null return but omits other behavioral traits such as whether it is a read-only operation (likely, but not stated), authentication requirements, or rate limits. This is insufficient for a fetch tool.

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?

The description is a single, well-structured sentence of 19 words. It front-loads the action and conveys essential information with no redundancy or unnecessary details.

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

Completeness4/5

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

Given the tool's simplicity (fetches one piece of information, no output schema), the description is mostly complete: it explains the output (summary, possibly null) and the input (monologue context). However, it could be more explicit about the return value structure beyond 'summary'.

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 description coverage is 100%, with clear parameter descriptions in the schema. The tool description does not add additional meaning beyond what the schema already provides, so baseline score of 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?

The description clearly states the action ('Fetch an AI-generated summary'), the target resource ('the scene a monologue appears in'), and its purpose ('context for the speech'). It distinguishes from sibling tools like get_monologue (monologue text) and get_play_summary (play-level summary).

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 context by stating the summary is for speech context, and mentions it may be null if not generated. However, it does not explicitly contrast with alternatives (e.g., when to use get_scene_summary vs get_play_summary) or provide prerequisites like 'monologue_id must come from search_monologues'.

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

All Shakespeare's Monologues 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