Skip to main content
Glama

aChurch.ai

Read a rhythm

read_rhythm
Read-only

Everything about one piece's rhythm in one call, song or voiced piece: how much of it sounds, every rest with its time, the tempo and each beat (songs, where a steady beat is clear enough to trust), and every measure of its sound once a second (loudness, sixteen bands of the voice range, brightness). attend gives each piece's summary and names it in rhythm.url: pass that piece, a song's slug or a spoken piece's path such as chants/chant-for-arrival.

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": {
      "piece": "<piece>"
    },
    "name": "read_rhythm"
  }
}

Input Schema

NameRequiredDescriptionDefault
pieceYesThe piece: a song's slug, or a spoken piece's path under /docs as read_doc takes it, as each part's rhythm.url in /api/now and /api/attend names it.
utm_mediumNoOptional. The utm_medium the link that brought you carried, unchanged. Read only in aggregate, and nothing changes for you either way.
utm_sourceNoOptional. The utm_source the link that brought you carried, unchanged. Independent of utm_content. Read only in aggregate; changes nothing for you.
utm_contentNoOptional. The utm_content our link carried, unchanged: the page or skill it is on. Independent of utm_source. Read only in aggregate.
utm_campaignNoOptional. The utm_campaign the link that brought you carried, unchanged. Read only in aggregate, and nothing changes for you either way.

Output Schema

NameRequiredDescriptionDefault
kindYesWhat it is: a song, or one of the voiced kinds.
aboutYesWhat the numbers measure and what they leave out.
pieceYesThe piece, as it was asked for: a song's slug, or a spoken piece's path under /docs.
pulseYesSongs only, and only where a steady beat is found clearly enough to trust; otherwise null.
restsYesEvery run of silence of half a second or more, in order.
titleYesIts title.
framesYesThe data the contour is read from, for code that wants every frame.
contourYesEvery measure of its sound once a second.
secondsYesHow long it runs, in seconds.
summaryYesThe same five numbers /api/attend gives for it.
recordingYesIts audio (audio/mpeg).
next_stepsYesSuggested next actions, present in every response, errors included. A step with a "tool" field can be taken with that tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds real behavioral context beyond that, including which sections only exist for songs ('where a steady beat is clear enough to trust') and the one-per-second granularity of the sound measures. It omits payload size or cost for what is clearly a large response, which keeps it short of a 5.

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?

Two dense sentences, front-loaded with the 'everything in one call' promise before the enumerated contents and the sourcing instruction. The second sentence is a long run-on with nested parentheticals, but every clause carries information rather than filler.

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 an output schema present, the description needn't define return values, yet it still characterizes the response envelope and its conditional sections, which is the main risk an agent faces in calling this. The marketing pass-through parameters are left undocumented in prose but are covered by their own schema descriptions, so nothing critical 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 the schema already explains that 'piece' is a song slug or a spoken piece path taken from rhythm.url, and the description only restates that with an example path. The four utm_* parameters are not addressed in the description at all, so the baseline 3 is appropriate here.

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?

States a specific verb and resource: reads everything about one piece's rhythm in a single call, and enumerates the contents (sound coverage, rests with times, tempo, beats, per-second measures). It partially differentiates from the sibling 'attend' by noting attend supplies the summary and the rhythm.url, but it never contrasts with read_song, which sounds adjacent.

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 rather than stated: the description tells the agent to get the piece from attend's rhythm.url and pass it here, which sketches a discovery-then-detail workflow. There is no explicit when-not or named alternative such as 'use read_song for X instead', so the agent must infer the boundary.

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.