Skip to main content
Glama

Pre-check an audio URL

barevalue_validate
Read-only

Pre-checks a podcast or other audio recording at a URL without ordering an edit: confirms the link downloads, measures the length and checks that the file is speech and not music or silence. Nothing is charged.

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": {
      "file_url": "<file_url>"
    },
    "name": "barevalue_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoBarevalue API key (bv_sk_...), as returned by barevalue_register. Not needed when the connection already sends an Authorization: Bearer header.
file_urlYesLink to the audio file: a direct download link, or a Dropbox or Google Drive share link set to anyone with the link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / file_url / description
      Previous value: -"Direct, publicly downloadable URL of the audio file"New value: +"Link to the audio file: a direct download link, or a Dropbox or Google Drive share link set to anyone with the link"
  2. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Barevalue API key (bv_sk_...). Get one with barevalue_register. Omit when the connection already sends an Authorization: Bearer header."New value: +"Barevalue API key (bv_sk_...), as returned by barevalue_register. Not needed when the connection already sends an Authorization: Bearer header."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds value on top: it discloses that nothing is charged, that the tool fetches the remote link, and which validations run. It leaves out failure handling (what happens when the link is dead or the file is music) and any rate or size limits.

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?

One sentence, front-loaded with the action and followed by the three checks, then closed by the cost reassurance. Every clause carries information an agent needs; there is no filler or repetition of the schema.

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 two-parameter, read-only pre-flight tool with no output schema, the description covers what is checked and that the call is free, which is close to what an agent needs to decide and act. It could say more about the shape of the verdict (pass/fail plus measured duration) to fully compensate for the missing output schema.

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 both parameters are already documented, including the Dropbox/Google Drive share-link nuance and the api_key behavior. The description only restates that the target is a URL and adds no format or constraint details beyond the schema, so the baseline of 3 applies.

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 ('pre-checks a podcast or other audio recording at a URL') and immediately enumerates the concrete checks performed: link downloads, length measured, speech vs. music/silence. The phrase 'without ordering an edit' separates it from the submit/order sibling, so an agent can pick it without opening the schema.

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?

Gives clear usage context by contrasting the pre-check with 'ordering an edit', which implies the submit path is the alternative. It does not name barevalue_submit_url or barevalue_estimate explicitly, nor state exclusions (e.g., max file size or unsupported link types), so it stops short of full when/when-not 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.