Skip to main content
Glama

Fiche d’un compositeur

fiche_compositeur
Read-only

Fiche Phono.Crescendo d’un compositeur : dates, nationalité, période, présentation, œuvres majeures, nombre de critiques Crescendo, Millésimes et Jokers, distinctions ICMA, et liste de ses disques critiqués (distingués en tête) avec liens vers les critiques.

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": {
      "compositeur": "<compositeur>"
    },
    "name": "fiche_compositeur"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNo
compositeurYesNom (ex. « Clara Schumann ») ou identifiant Phono (ex. « johann-sebastian-bach »)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description adds real behavioral value beyond that by disclosing the shape of the result: reviewed discs are returned with award-winning ones listed first and include links to the reviews. It does not mention pagination, truncation behavior, or what happens when a composer is not found, which is notable given there is no output schema.

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?

A single dense sentence that front-loads the resource and then enumerates contents in a scannable order. It is long but every clause names a concrete returned field, so little is wasted; a light structural break would improve readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does much of the work by listing returned fields and the ordering of reviewed discs, which is the right call. However, for a two-parameter tool it leaves 'limite' entirely unexplained and says nothing about missing-composer behavior, leaving a meaningful gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only the 'compositeur' parameter is documented in the schema (name or Phono identifier), giving 50% coverage. The description does not explain the 'limite' parameter at all — an agent must guess that it caps the number of reviewed discs, and the default of 15 with a max of 50 is left unaddressed. The description therefore does not compensate for the coverage gap.

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?

The description names a specific resource (a composer's Phono.Crescendo profile) and enumerates exactly what the record contains: dates, nationality, period, presentation, major works, review counts, ICMA distinctions, and reviewed discs. That content list distinguishes it from siblings like chercher_critiques or the palmares_* tools, which are ranking/search oriented. The only weakness is that the verb is nominal ('Fiche'), so the retrieval action is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus chercher_critiques or the palmares tools, and no stated prerequisites or exclusions. An agent can infer it is a per-composer lookup, but nothing in the text routes it away from alternatives or clarifies whether it should be used before or instead of a review search.

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.