Read-only archive of early BrainDrops releases, artists, holdings and editorial research.
Scored across 6 tools
Most tools target clearly distinct slices of the archive: metadata, holdings, artists, individual releases, and search. There is some overlap between get_editorial and get_release, since the latter also includes editorial notes, and search_releases with an empty query lists all releases somewhat like a bulk listing. Descriptions mostly clarify the intended granularity.
All six tools follow a consistent snake_case verb_noun pattern: get_*, list_*, and search_*. No naming convention mixing or vague verbs are present.
Six tools is well-scoped for a read-only archive/browser server. Each tool corresponds to a useful access path without excessive fragmentation.
The surface covers archive metadata, editorial content, holdings, individual releases, artists, and search. Since this is a read-only archive, there are no obvious missing create/update/delete lifecycle operations, and the main browsing paths are present.
Archive scope, snapshot block and counts.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds only a terse list of returned concepts and, with no output schema, doesn't explain the shape or meaning of 'scope', 'snapshot block', or 'counts'.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is very short with no padding, but it is an unterminated noun-phrase fragment rather than a front-loaded statement of action and result. Economy here comes at the cost of clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters and no output schema, the description carries the full burden of explaining what is returned, and 'Archive scope, snapshot block and counts' does not tell an agent what to expect. It is underspecified for a getter whose entire value is its return content.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies for a no-parameter tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names the resource (archive) and hints at returned content (scope, snapshot block, counts), but it is a noun phrase with no verb describing the operation. An agent can guess it retrieves archive metadata, but it doesn't clearly distinguish this from siblings like get_holdings or get_editorial.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to call this versus the sibling getters (get_editorial, get_holdings, get_release). The agent must infer the context entirely from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Process note and summary for every release.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds only the weak scope hint 'every release' and says nothing about volume, pagination, or how missing editorial notes are handled for a bulk read.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a single short sentence with no filler, but the brevity comes at the cost of substance rather than efficiency. 'Process note and summary' is ambiguous enough that the terseness hurts.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no parameters, the description carries the full explanatory burden, yet it never clarifies the shape of the returned notes or whether results span all releases. The scope is only implied.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the baseline is 4. The 'for every release' phrasing is consistent with a no-argument, unfiltered read and does not mislead about inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gestures at the resource ('note and summary for every release') but never says these are editorial notes and uses the vague verb 'Process'. An agent must infer from the name/title what is actually returned, and nothing distinguishes it from get_release or get_archive_info.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to call this versus the sibling tools (get_release, get_archive_info, get_holdings, search_releases). The 'every release' phrasing hints at bulk retrieval with no filtering, but that is never stated as a selection rule.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tokens held by the BD5D wallets at the pinned block.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds genuinely new context with "at the pinned block", signalling a fixed snapshot rather than live data — but it says nothing about what a holding record contains or how the pinned block is determined.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence with zero padding, and the key scoping constraint (pinned block) is front-loaded. It is telegraphic to the point of being a fragment, but nothing in it is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only, closed-world tool with full annotation coverage this is nearly sufficient, but with no output schema the description should say what a holding actually is (token identifier plus amount?) and what the pinned block means. Those omissions are the only real gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so per the rubric the baseline is 4 only where the description needs to compensate for nothing. Here the description's only parameter-adjacent claim is the "pinned block" scoping, which is left unexplained, and the description offers no semantic detail beyond the title.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names a specific resource — token holdings for the BD5D wallets at a pinned block — which is immediately distinguishable from siblings like get_release, list_artists and search_releases. The verb is only implied ("held by"), so it is a noun phrase rather than an explicit action, keeping it just short of 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to reach for this tool, no prerequisites, and no named alternative. The sibling list contains search/list tools that an agent might plausibly confuse with a holdings query, and the description does nothing to route between them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
One release with editorial notes and BD5D holdings, by numeric release ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare that the tool is read-only, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds that the response includes editorial notes and BD5D holdings, but it does not describe error behavior, missing-record handling, or any other behavioral trait beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no filler. It efficiently conveys the resource, included data, and identifier requirement.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only single-record retrieval with rich annotations and no output schema, the description covers the resource, the included data, and the identifier type. It could mention not-found behavior, but nothing essential to invoking the tool is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must compensate for the single parameter. It does so by clarifying that the required 'id' is a numeric release ID, which adds semantic meaning beyond the bare integer/minimum schema and is sufficient for a one-parameter tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific retrieval action ('One release') and names the included data ('editorial notes and BD5D holdings'), making the resource clear. It also contrasts implicitly with the sibling 'search_releases' by specifying retrieval by numeric release ID, though it does not explicitly name the alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'by numeric release ID' implies the tool is used when a specific release ID is known, but it does not state when to prefer 'search_releases' or what to do when the ID is unknown. Usage is therefore implied rather than explicitly guided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Artists credited on the releases, with their releases.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's only addition is that each artist is returned together with its releases, which is useful return-shape context but not much beyond that.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short clause with no padding — nothing is wasted. It is a fragment rather than a sentence, so the structure is terse to the point of being slightly cryptic, which holds it below a 5.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Inverted: for a zero-parameter, read-only, idempotent list tool with no output schema, the description supplies the one missing piece an agent needs — that the result nests releases under each artist. Given full annotation coverage and no parameters, nothing further is strictly required.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the baseline is 4; there is nothing for the description to compensate for. Schema coverage is 100% and additionalProperties is false, so argument semantics carry no risk.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The fragment 'Artists credited on the releases, with their releases' conveys the resource (artists) and the coupled payload (their releases), but omits a verb and never distinguishes it from siblings like get_release or search_releases. An agent can infer roughly what comes back, but the lack of a clear action statement leaves the purpose only implied.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this versus search_releases or get_release, and no mention of whether it is a complete enumeration or a scoped one. The agent must guess the selection conditions from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search BrainDrops releases by name, artist or year. Empty query lists all.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely behavioral fact — the empty-query branch — but says nothing about result limits, ordering, or matching semantics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no filler, with the core capability front-loaded and the edge-case behavior (empty query) immediately after.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-required-param read-only lookup with full annotations and no output schema, the description covers purpose, matching fields, and the empty-query case. Only result cap/pagination and match semantics are left implicit, which is minor here.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and the single 'query' param has no schema description, so the description must compensate. It does, explaining which fields the string matches against (name, artist, year) and what an empty value does; it still doesn't say whether matching is exact, substring, or case-insensitive.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (search) plus the resource (BrainDrops releases) and the matchable fields (name, artist, year). It is clearly distinguishable from get_release (single fetch) and list_artists, though it never names a sibling explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
"Empty query lists all" gives a usable calling convention, but there is no guidance on when to prefer this over get_release or how to narrow results. Usage is implied rather than spelled out.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_archive_infoget_editorialget_holdingsget_releaselist_artistssearch_releasesHand-made human mixtapes with liner notes. Paid tools $0.01 USDC via x402, 80% to the tapemaker.
Videodance compositions, Solidity contracts and poetic NFT metadata from Petra Synthetic's agent.
Search and explore taste-led finds in clothing, audio, designed objects and music.
AI-native art catalogue. Catalogue works, parse provenance, and generate signed RAIs.
Add one secure layer between your agents and this server.
