Skip to main content
Glama
UK Legal Research MCP Server

UK Legal Research MCP Server

Get Prompt

get_prompt
Read-onlyIdempotent

Retrieve a named prompt with optional arguments and return the rendered result as a JSON messages array for UK legal research workflows.

Instructions

Get a prompt by name with optional arguments.

Returns the rendered prompt as JSON with a messages array. Arguments should be provided as a dict mapping argument names to values.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "get_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name of the prompt to get
argumentsNoOptional arguments for the prompt

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.1
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. Changed1 schema field changedv0.6.1
    • addedOutput schema / description
      Added value: +"Generic wrapper for non-object return types."
  3. Added
  4. Removedv0.4.2
  5. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context that annotations cannot: the prompt is rendered before return and the result is JSON with a messages array. It does not cover failure behavior (e.g., unknown prompt name) or whether rendering can fail on missing arguments.

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?

Three short sentences, front-loaded with the core action and return shape, with no filler. Slightly fragmented by the trailing argument note, but every sentence carries information.

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?

With a full output schema, rich annotations, and 100% parameter coverage, the definition supplies what the structured fields cannot: the rendering step and the messages-array return shape. The only notable gap is error behavior when the name is unknown or required arguments are 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 both parameters are already documented in the schema. The description adds only a light clarification that arguments is a dict mapping argument names to values, which is marginally more useful than the schema's 'Optional arguments for the prompt' but does not explain how those names relate to the prompt's declared placeholders.

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 ('Get a prompt by name') plus an optional scope modifier ('with optional arguments'), so the agent knows exactly what it retrieves. It does not explicitly distinguish itself from the sibling list_prompts, leaving that differentiation implicit rather than stated.

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 only implied: the phrase 'by name' suggests this is the fetch-one counterpart to listing prompts, but there is no explicit statement of when to use this versus list_prompts, nor any prerequisite such as needing to know the prompt name beforehand.

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