Skip to main content
Glama

Prompt Fallback (load-briefing)

load-briefing
Read-only

Returns structured fallback errors when a journal briefing is invoked as an MCP tool instead of a prompt, including codes, details, and suggested fixes.

Instructions

Fallback handler for load-briefing when invoked as an MCP tool instead of an MCP prompt.

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": "load-briefing"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
use_test_dbNo
aggregated_errorsNoDetails of individual errors in a multi-step operation

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv9.1.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties
      Added value: +{
      +  "aggregated_errors": {
      +    "description": "Details of individual errors in a multi-step operation",
      +    "items": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "message": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "message"
      +      ],
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "category": {
      +    "description": "Error category (validation, query, connection, internal)",
      +    "type": "string"
      +  },
      +  "code": {
      +    "description": "Error code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)",
      +    "type": "string"
      +  },
      +  "details": {
      +    "additionalProperties": {},
      +    "description": "Additional error context",
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  "error": {
      +    "description": "Human-readable error message",
      +    "type": "string"
      +  },
      +  "recoverable": {
      +    "description": "Whether the error is recoverable",
      +    "type": "boolean"
      +  },
      +  "suggestion": {
      +    "description": "Suggested fix for the error",
      +    "type": "string"
      +  },
      +  "use_test_db": {
      +    "type": "boolean"
      +  }
      +}
    • addedOutput schema / additionalProperties
      Added value: +{}
    • addedOutput schema / properties / aggregated_errors
      Added value: +{
      +  "description": "Details of individual errors in a multi-step operation",
      +  "items": {
      +    "additionalProperties": {},
      +    "properties": {
      +      "message": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "message"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / category
      Added value: +{
      +  "description": "Error category (validation, query, connection, internal)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / code
      Added value: +{
      +  "description": "Error code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / details
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Additional error context",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / error
      Added value: +{
      +  "description": "Human-readable error message",
      +  "type": "string"
      +}
    • addedOutput schema / properties / recoverable
      Added value: +{
      +  "description": "Whether the error is recoverable",
      +  "type": "boolean"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "$schema": "https://json-schema.org/draft/2020-12/schema"
      -}
    • addedOutput schema / properties / suggestion
      Added value: +{
      +  "description": "Suggested fix for the error",
      +  "type": "string"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "result"
      -]
  2. First observedv9.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds no behavioral context beyond that: it does not say what happens on invocation, what the error-shaped payload represents, or whether the fallback can fail. With annotations present the bar is lower, but nothing of value is contributed.

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?

A single, short sentence with no padding, and the key qualifier (fallback, tool-vs-prompt) is front-loaded. It is efficient, though the terseness is achieved by omitting essential information rather than by editing out waste.

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

Completeness2/5

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

The tool has 8 parameters including nested objects and an output schema, yet the description is one sentence that explains nothing about the contract. An agent cannot determine from this text what the tool does, why its inputs look like an error object, or what to do with the result — substantial gaps for a tool of this complexity.

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 88% across 8 parameters, so the schema itself carries the semantics and the baseline of 3 applies. The description adds nothing about parameters, which is notable because the schema exposes error fields (code, error, recoverable, aggregated_errors) that are surprising for a briefing-loading tool and arguably need explanation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the title almost verbatim: it says this is a "fallback handler" for something called `load-briefing`, but never states what loading a briefing does or what the tool produces. It only clarifies that the call is happening via the tool route rather than the prompt route, which is meta-information rather than a purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is a hint that this path exists only when `load-briefing` is invoked as an MCP tool instead of a prompt, which implicitly signals an agent should normally prefer the prompt. However, there is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling tools, so the guidance is inferential at best.

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

Deploy Server

Other Tools