Origine Paris

Brand identity (deprecated)

get_brand_identity

Read-onlyIdempotent

DEPRECATED, removed in 1.0.0: call get_maison with section "overview" and lang "fr" or "en" instead. Until then this alias still answers exactly as before. Returns the identity of Origine Paris, the Parisian fine jewellery house of recycled 18ct gold and IGI-certified lab-grown diamonds. Use it for ready-to-use brand facts (trading name, legal identity (SIREN), descriptions, positioning, the by-appointment address at 21 rue de la Paix, contacts, official profiles); for the underlying source markup use get_jsonld_graph, and for the catalogue use search_catalogue, not this. Read-only and side-effect-free: it returns a structured identity object plus a text copy, with the sources, the index timestamp and the canonical URL, taken from the site JSON-LD and Wikidata and served as published; absent values are reported as "unknown", never invented.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Tool-specific result object, read-only and derived from public sources.
`notices`	No	Present on deprecated aliases: the replacement to call.
`sources`	Yes	URLs of the public sources backing this response: site pages, Wikidata and the published llms.txt.
`canonical`	Yes	Canonical Origine Paris website URL.
`generated_at`	Yes	ISO 8601 timestamp of the served index generation.

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations indicating read-only and idempotent, the description adds that it returns a structured object plus a text copy, includes sources, timestamp, and canonical URL, and specifies that absent values are reported as 'unknown' rather than invented. This provides valuable transparency about output behavior and data handling.

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 well-structured and front-loads the most critical information (deprecation and replacement). Although it's a bit lengthy, each sentence contributes necessary details about usage, alternatives, and output. It is concise given the complexity and avoids redundancy.

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?

The description covers all necessary aspects: what the tool returns, when to use it, what alternatives exist, and how it handles missing values. It even describes the output structure and metadata. This provides a complete picture for an agent to decide and call the tool correctly.

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 tool has no parameters, so the schema is empty with 100% coverage. The description doesn't mention parameters, but since there are none, it's not needed. The baseline for zero params is 4, and there is no additional parameter-related information to add, so this score is appropriate.

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 states the tool's purpose: it returns the identity of Origine Paris. It distinguishes itself from siblings by noting it's deprecated and that get_maison should be used instead, and explicitly lists alternative tools for other uses, making its role specific and clear.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: it directs users to use this for ready-to-use brand facts, and instructs them to use get_jsonld_graph for underlying markup and search_catalogue for catalogue searches, with a 'not this' note. This clarifies when to choose this tool over its siblings.

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

All Origine Paris tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation3/5

The deprecated tools (get_brand_identity, get_entity_graph, get_founders, get_jsonld_graph, get_llms_context, get_person_profile) are aliases that overlap heavily with get_maison, but the deprecation notices clearly redirect to the new consolidated tool, reducing ambiguity. However, there is still some overlap between get_maison and search_catalogue for catalogue queries, and get_maison with 'jsonld' vs get_jsonld_graph could confuse. The distinct purpose of each deprecated tool is clear from the description, but the coexistence of deprecated aliases and new consolidated tool adds mild confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (get_*, search_*) with clear, descriptive nouns (brand_identity, entity_graph, founders, jsonld_graph, llms_context, maison, person_profile, catalogue). The pattern is uniform and predictable, and the naming clearly indicates what each tool retrieves.

Tool Count4/5

With 8 tools, the count is within the typical range (3-15) and each tool has a defined role. However, six of the eight tools are deprecated aliases that will be removed, leaving only two effective tools (get_maison and search_catalogue). This makes the count slightly heavier than necessary, though the deprecation strategy with aliases is reasonable for migration.

Completeness3/5

The tool surface covers brand identity, entity graphs, founder profiles, raw JSON-LD, agent context, and catalogue search, which is comprehensive for the domain. However, there are gaps: no tools for updating or managing data (read-only is noted), and the consolidation into get_maison might miss some niche queries that the deprecated tools offered. The core read-only coverage is good, but there is no write or update capability, which might be expected for a full lifecycle.

Resources

Need Help?