Gold & Silver Company

Grille de rachat du jour

cotation

Read-onlyIdempotent

Today's public buying grid of Gold & Silver Company, timestamped: gold by fineness (9K, 14K, 18K, 22K in EUR per gram; 24K/999 refers to the live rate) or by coin/bar (napoleon_20f, pesos_50, argent_lingot_1kg in EUR per piece). Optional weight in grams or number of pieces gives an indicative amount; objets quotes several items in one call with a total. The firm price is set at the office after weighing and fineness check. Source: the public grid on the website, never internal tools.

Input Schema

TableJSON Schema

Name	Required	Description
`titre`	No	Gold fineness: 9K, 14K, 18K, 22K, 24K (or 375, 585, 750, 916, 999)
`langue`	No
`nombre`	No	Number of pieces (coins or bars)
`objets`	No	Several items in one call: [{titre\|produit, poids_g\|nombre}, …] → lines and indicative total
`poids_g`	No	Weight in grams (gold by fineness)
`produit`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`metal`	No
`texte`	No
`unite`	No
`objets`	No
`source`	No
`libelle`	No
`prix_eur`	No
`quantite`	No
`indicatif`	No
`disponible`	Yes
`grille_publiee_le`	No
`horodatage_reponse`	No
`total_indicatif_eur`	No
`montant_indicatif_eur`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 17, 2026

addedInput schema / properties / objets

Added value: +{
+  "description": "Several items in one call: [{titre|produit, poids_g|nombre}, …] → lines and indicative total",
+  "items": {
+    "properties": {
+      "nombre": {
+        "type": "integer"
+      },
+      "poids_g": {
+        "type": "number"
+      },
+      "produit": {
+        "type": "string"
+      },
+      "titre": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedOutput schema / properties / objets
```
Added value: +{
+  "type": "array"
+}
```
addedOutput schema / properties / total_indicatif_eur
```
Added value: +{
+  "type": "number"
+}
```

First observedSep 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds valuable behavioral nuance: results are timestamped, weights/piece counts yield only an indicative amount, the firm price is determined in the office after verification, and data comes from the public web grid rather than internal tools. This meaningfully shapes expectations beyond the annotations.

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?

The description is front-loaded with the core resource and is dense but non-repetitive. Every sentence earns its place: asset categories, units, optional calculation behavior, the firm-price caveat, and the public-source constraint. No filler or redundant restatement is present.

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 read-only quotation tool with an output schema, the description is complete: it covers all product categories, units, optional parameters, aggregate behavior for objets, the indicative nature of calculations, and the data-source constraint. An agent has enough information to invoke the tool correctly and interpret its results appropriately.

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?

The description adds substantial meaning beyond the schema: it maps finenesses to EUR per gram, products to EUR per piece, clarifies 24K/999 as the live rate, and explains that poids_g/nombre produce an indicative amount and objets returns lines plus a total. The main unaddressed parameter is langue, though its enum is self-explanatory; with 67% schema coverage, the description compensates well.

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 clearly identifies the tool as Gold & Silver Company's current-day public buying grid .. It enumerates supported asset types (gold finenesses, coins, bars) and units, and the phrase 'today's' plus 'timestamped' distinguishes it from siblings like cours_historique. The resource and scope are unambiguous despite using a noun phrase rather than a verb.

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?

The description implies when to use the tool: for today's public buyback rates and indicative valuations. The temporal qualifier 'du jour/timestamped' and the source caveat ('public grid on the website, never internal tools') provide clear context. It does not explicitly name alternatives such as cours_historique, so exclusions are implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gold & Silver Company tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?