Skip to main content
Glama

Chercher des critiques de disques

chercher_critiques
Read-only

Recherche dans plus de 5 000 critiques de disques de musique classique publiées par Crescendo Magazine (Belgique) depuis 1993. Tous les critères sont facultatifs et combinables (ex. « Bach chez Harmonia Mundi », « Mahler par Paavo Järvi », « les Jokers de 2024 », « Winterreise »). Renvoie titre, label, année, compositeurs, distinction éventuelle (Millésime, Joker) et lien vers la critique complète.

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": "chercher_critiques"
  }
}

Input Schema

NameRequiredDescriptionDefault
anneeNoAnnée de publication de la critique
labelNoLabel discographique (ex. « Alpha Classics », « Harmonia Mundi »)
texteNoMots à chercher dans le titre de l’album ou de la critique (œuvre, interprète, ensemble…)
limiteNo
interpreteNoInterprète : chef, soliste, orchestre ou ensemble (ex. « Paavo Järvi », « Orchestre National de Lille »)
compositeurNoNom du compositeur (ex. « Beethoven », « Hildegard von Bingen »)
distinctionNoUniquement les disques distingués par la rédaction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/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 genuine behavioral context beyond that: dataset size (5 000+ reviews), coverage period (since 1993), publisher, and exactly which fields are returned (titre, label, année, compositeurs, distinction, lien). It does not mention result-set behavior such as the default/maximum result cap, which the schema carries but the prose never reinforces.

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?

Three sentences, front-loaded with corpus and scope, then the combinatorial rule with examples, then the return payload. Nothing is redundant with the title, and every sentence contributes distinct information an agent needs.

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?

Seven optional parameters, no required fields, no output schema — yet the description names the returned fields so the agent knows what to expect. Corpus boundaries, optionality, combination semantics, and result shape are all covered, leaving nothing essential an agent must guess before calling.

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?

With 86% schema description coverage the baseline is 3, and the description earns above that by illustrating what individual parameters mean in combination: 'Bach chez Harmonia Mundi' maps to compositeur+label, 'Mahler par Paavo Järvi' to compositeur+interprete, 'les Jokers de 2024' to distinction+année, and 'Winterreise' to texte. The only gap is that 'limite' is never mentioned in prose, though the schema documents it with a default and cap.

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 ('Recherche dans plus de 5 000 critiques de disques'), plus corpus scope (Crescendo Magazine, since 1993) and returned fields. An agent immediately knows this is a full-text/field search over reviews rather than a lookup. It does not explicitly differentiate itself from siblings like palmares_crescendo, which also surface distinctions (Millésime, Joker), leaving a small ambiguity.

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?

'Tous les critères sont facultatifs et combinables' tells the agent it can call with zero arguments and combine any subset, which is real usage guidance. The four worked examples ('Bach chez Harmonia Mundi', 'Mahler par Paavo Järvi', 'les Jokers de 2024', 'Winterreise') effectively demonstrate how to combine criteria. There is no explicit routing to alternatives or statement of when not to use this tool, so it falls short of a 5.

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.