SharpSyn

where_is_it_made

Read-only

Where a compound is produced, from the SharpSyn Chemical World Map: the known production sites (name, operator, country, coordinates), how they spread over countries (share per country, single-site warning), the confidence and source of each entry, and the page and map links to cite. Site products from public research are estimates; operators marked 'unclaimed' have profiles built from public sources, not managed by them. Each site has the status of the line (operating, closure_announced, idle, planned, under_construction, closed, with dates), the operator of that line and its capacity (t/a with basis, year and reference substance). By default only lines producing now; include_inactive adds the rest. Shares per country by site count and by capacity, and the coverage: how many sites are known, how many with capacity, and what share of world production that is where the world production is on record.

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": {
      "identifier": "<identifier>"
    },
    "name": "where_is_it_made"
  }
}

Input Schema

Name	Required	Description	Default
`identifier`	Yes
`include_inactive`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds substantial extra context beyond that: data provenance (public research estimates), operator caveats ('unclaimed'), status categories with dates, and coverage metrics. This is meaningful behavioral disclosure, though it omits any mention of response format or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a dense, run-on block with nested parenthetical lists and multiple clauses per sentence. While front-loaded with the core purpose, it is far longer than necessary and poorly structured for scanning, burying key behavioral details in the middle.

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?

There is no output schema, so the description compensates by enumerating return contents extensively: site attributes, country shares, confidence, links, statuses, and coverage statistics. This is nearly complete for a read-only lookup, though the unexplained identifier parameter prevents a perfect score.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains include_inactive's effect ('adds the rest'), but the required 'identifier' parameter is never described—no format, accepted values, or examples. With a required parameter completely undocumented, this is a significant 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 opening sentence states the resource clearly: production sites for a compound, drawn from a named dataset. It enumerates the return contents in detail, so an agent can tell it is a lookup of manufacturing locations. However, it never distinguishes itself from siblings like value_chain or get_compound, leaving overlap unresolved.

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?

The only usage guidance is a parameter note: 'By default only lines producing now; include_inactive adds the rest.' There is no indication of when to choose this tool over get_compound, value_chain, or list_suppliers, and no exclusions or prerequisites are stated.

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

All SharpSyn 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?