Skip to main content
Glama

Besorah — the Bible in Hebrew, Greek, Aramaic and English

Songs and prayers in Scripture

list_songs
Read-onlyIdempotent

Returns the songs and prayers inside Scripture (the Song of the Sea, Hannah's prayer, the Magnificat…), each with its name, Hebrew title, kind (victory, prophetic, thanksgiving, boast, prayer, work song, blessing, lament or hymn), passage reference and link. kind narrows the list; otherwise the whole list comes back in one piece. Use when the user asks which songs and prayers appear inside Scripture, such as the Song of the Sea or the Magnificat.

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

Input Schema

NameRequiredDescriptionDefault
kindNokind of song or prayer, e.g. victory, lament, prayer, blessing, hymn, thanksgiving
formatNooptional: json (default) or markdown (compact, readable)
max_charsNooptional: cap the answer at about this many characters (lists are shortened and marked truncated; use offset/nextOffset to get the rest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / kind / description
      Added value: +"kind of song or prayer, e.g. victory, lament, prayer, blessing, hymn, thanksgiving"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the description is free to add the return shape it uniquely supplies: each entry carries name, Hebrew title, kind, passage reference and link. It also discloses the filter-vs-full-list behavior ('otherwise the whole list comes back in one piece'), which is real behavioral context beyond the annotations.

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?

Purpose and return contents are front-loaded, and the usage trigger sits last where an agent scanning for routing cues will look. The parenthetical taxonomy is long but earns its place by defining valid kind values; nothing is redundant.

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?

With no output schema, the description carries the return-value burden and does so by listing every field returned. Three optional parameters, one enum, and a simple read-only list operation are all adequately covered, with truncation semantics already handled in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description goes further by explaining that 'kind' narrows the result set while omitting it returns everything, and it enumerates the kind taxonomy more fully than the schema's example list (adding boast, work song, prophetic). Format and max_chars semantics remain solely in the schema, which is acceptable given full coverage.

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 a specific verb and resource ('Returns the songs and prayers inside Scripture') and enumerates concrete instances (Song of the Sea, Hannah's prayer, the Magnificat), which makes the scope unmistakable against sibling list_books or list_questions.

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

Usage Guidelines4/5

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

The final sentence gives a clear triggering condition ('Use when the user asks which songs and prayers appear inside Scripture') with example queries, which is enough to route the agent correctly. It does not name an alternative tool or state when not to use it, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources