Skip to main content
Glama

Rechercher dans le catalogue

search_catalogue
Read-only

Cherche dans le catalogue de la Ravel Edition (volumes, éditions révisées, orchestrations). Renvoie titre, volume, année de composition et d'édition, durée, effectif, ISMN et adresse de la fiche. Sans paramètre, renvoie tout le catalogue.

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

Input Schema

NameRequiredDescriptionDefault
queryNoMots à chercher : titre, volume, effectif, ISMN… (facultatif)
categoryNoFiltre de catégorie, par exemple orchestre, concerto, chambre, piano (facultatif)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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, openWorldHint=false), so the description only needs additive context — and it delivers: it enumerates the returned fields (titre, volume, année de composition/édition, durée, effectif, ISMN, adresse de la fiche) and discloses the empty-parameter default of returning the entire catalogue. It stops short of saying anything about result size limits or pagination, which matters for a tool that can return everything.

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 sentences, front-loaded with the purpose and corpus, with zero filler. The returned-field enumeration is a long list but earns its place given there is no output schema; only minor trimming would be possible.

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?

For a two-optional-parameter, read-only search tool with no output schema, the description covers purpose, corpus scope, returned fields, and default behavior under missing parameters — everything an agent needs to decide whether to call it and what to expect back.

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% and both parameters are documented in the schema (query covers titre/volume/effectif/ISMN; category gives examples like orchestre, concerto, chambre, piano). The description adds return-value information but nothing about parameter syntax, matching behavior, or how query and category combine — so the baseline 3 applies.

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 ('Cherche') and a well-scoped resource (le catalogue de la Ravel Edition), plus the sub-corpora covered (volumes, éditions révisées, orchestrations). It is distinguishable from get_work (single work lookup), list_orchestras, and latest_news, but it never names those siblings explicitly to force the distinction.

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?

States one useful usage rule — 'Sans paramètre, renvoie tout le catalogue' — which tells the agent how the no-filter case behaves. It gives no guidance on when to prefer this over get_work for a known title, nor on when a filtered search is expected instead of a full dump.

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