Shakespeare's Monologues

get_monologue

Read-only

Fetch one monologue's catalogue entry by its numeric id. Follow the returned url for the full text.

Input Schema

Name	Required	Description
`id`	No	The monologue's numeric id (from search_monologues).
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`monologue_id`	No	Deprecated alias for `id`.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 11, 2026

changedInput schema / properties / context / description

Previous value: -"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.\""New value: +"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "context"
-]New value: +[
+  "context",
+  "llm_model"
+]

Changed2 schema fields changedOct 3, 2026

changedInput schema / properties / id / type

Previous value: -[
-  "number",
-  "string"
-]New value: +[
+  "number",
+  "string",
+  "null"
+]

changedInput schema / properties / monologue_id / type

Previous value: -[
-  "number",
-  "string"
-]New value: +[
+  "number",
+  "string",
+  "null"
+]

Changed2 schema fields changedOct 3, 2026

changedInput schema / properties / id / type

Previous value: -"integer"New value: +[
+  "number",
+  "string"
+]

changedInput schema / properties / monologue_id / type

Previous value: -"integer"New value: +[
+  "number",
+  "string"
+]

Changed3 schema fields changedJul 27, 2026

changedInput schema / properties / id / description

Previous value: -"The monologue's numeric id."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"
+]

Changed3 schema fields changedJul 21, 2026

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: -[
-  "id"
-]New value: +[
+  "id",
+  "context"
+]

First observedJul 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: the response is a catalogue entry rather than the monologue text, and the full text lives behind the returned `url`. That return-shape disclosure is the main value-add.

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 tight sentences with no filler; the retrieval action and key are front-loaded and the follow-up pointer to full text comes second. Nothing is wasted.

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?

For a read-only lookup with no output schema and fully documented parameters, the description covers the essentials: what is returned (catalogue entry) and how to get the underlying text (url). It is slightly thin on relationship to siblings, but nothing needed to invoke it correctly 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 description coverage is 100%, so every parameter (id, context, llm_model, deprecated monologue_id, conversation_id) is already documented in the schema. The description only restates that `id` is numeric and sourced from search_monologues, adding little beyond the schema, so the 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?

Specific verb (Fetch) plus resource (one monologue's catalogue entry) and the key retrieval key (numeric id). It also implicitly distinguishes the catalogue record from the full text, which separates it from siblings like get_paraphrased_monologue and search_monologues. No sibling is named explicitly, so it falls short of a 5.

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?

Usage is implied by 'by its numeric id' and the schema note that the id comes from search_monologues, but the description itself offers no explicit when-to-use or when-not-to-use guidance against siblings such as get_monologue_of_the_day or random_monologue. The only concrete guidance is the follow-the-url instruction for retrieving full text.

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 tools Inspect

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.

get_monologue

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources