Skip to main content
Glama

GetEverwear second-hand clothing catalogue

Fiche d'une pièce

fiche_piece
Read-onlyIdempotent

Détail d'une pièce par son handle (donné par chercher_pieces) : disponibilité, prix, taille, état, marque, couleur et matière si connues, mesures, description, photos et lien de la fiche.

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": {
      "handle": "<handle>"
    },
    "name": "fiche_piece"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesHandle de la pièce, tel que renvoyé par chercher_pieces, ou l'adresse complète de sa fiche.

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by listing the returned fields and flagging that attributes like brand, color and material appear only 'si connues', warning the agent that fields may be absent.

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?

A single front-loaded sentence: purpose, handle source, then returned content. The field enumeration is long but each item is substantive for a tool with no output schema, and there is no filler.

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?

With no output schema, the description usefully enumerates what comes back and notes optional fields, which is exactly what the agent needs. It stops short of mentioning error behavior for an invalid or stale handle, a minor remaining gap.

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 coverage is 100% and the handle parameter already documents its max length and that it may be a full fiche URL. The description adds only the provenance hint (handle given by chercher_pieces), so the schema does the heavy lifting and the baseline 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?

The description states a specific verb and resource ('Détail d'une pièce') plus the identifying key ('par son handle'), and it explicitly differs from the search sibling by noting the handle comes from chercher_pieces. An agent can distinguish this detail-fetch from the search tool without opening either 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?

It clearly routes the agent: this tool is for fetching full details of a piece whose handle you already have from chercher_pieces, which implies search-first usage. It lacks an explicit 'do not use this to search/browse' exclusion, but the sourcing constraint gives adequate context.

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