Skip to main content
Glama

scip_notification_dossier_screener

Read-onlyIdempotent

[ECHA SCIP database dossier completeness screener. Deterministic validation, read-only, side-effect free]. Screens article SCIP notification dossiers under Directive 2008/98/EC Article 9(1)(i), verifying CN/TARIC codes, Candidate List SVHC ranges, material categories, and safe use instructions for IUCLID 6 submission. Usage: Submit planned SCIP notification payload to verify mandatory data fields before submitting to ECHA Submission Portal. Returns: JSON object with { articleName: string, isScipNotificationMandatory: boolean, dossierReadinessStatus: string, validationChecklist: object, missingMandatoryFields: array }.

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": {
      "articleName": "<articleName>",
      "primaryArticleIdentifierType": "<primaryArticleIdentifierType>",
      "primaryArticleIdentifierValue": "<primaryArticleIdentifierValue>",
      "primaryArticleCategoryCnTaricCode": "<primaryArticleCategoryCnTaricCode>",
      "productionInEu": "<productionInEu>",
      "candidateListSubstances": "<candidateListSubstances>",
      "safeUseInstructionsProvided": "<safeUseInstructionsProvided>"
    },
    "name": "scip_notification_dossier_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
articleNameYesCommercial or technical name of the article
productionInEuYesWhether the article was manufactured in the EU or imported
candidateListSubstancesYesSVHC candidate substances present > 0.1% w/w
safeUseInstructionsSummaryNoSummary of safe use instructions for waste operators
safeUseInstructionsProvidedYesWhether proper safe use instructions are included
primaryArticleIdentifierTypeYesPrimary identifier type
primaryArticleIdentifierValueYesPrimary identifier value/code
primaryArticleCategoryCnTaricCodeYes4 to 10 digit Combined Nomenclature / TARIC customs code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare read-only and idempotent behavior, and the description adds that validation is deterministic and side-effect free plus the specific compliance checks performed. It does not discuss validation limits, failure modes, authentication needs, or rate limits, so it adds useful but limited behavioral context beyond annotations.

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?

The description is front-loaded with the tool's purpose, then usage, then return shape, and is appropriately sized for a compliance screener. The bracketed preamble partly repeats the annotations' read-only claim, but it does not create significant clutter.

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 supplies the return object shape and explains the legal and submission context. Combined with the fully documented input schema, it gives enough information to invoke the tool correctly, though it could say more about validation limits or interpretation of dossierReadinessStatus.

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 description coverage is 100%, so the input schema already defines all eight parameters and the enum for concentration ranges. The description mentions domain concepts like CN/TARIC codes and SVHC ranges but adds no parameter-specific meaning beyond the schema.

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 states a specific verb and resource: it screens article SCIP notification dossiers for completeness and verifies CN/TARIC codes, SVHC ranges, material categories, and safe use instructions. It is clearly not a generic threshold tool, but it does not explicitly distinguish itself from sibling screeners such as reach_svhc_threshold_screener.

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 gives a clear usage context: submit a planned SCIP notification payload to verify mandatory fields before submitting to the ECHA Submission Portal. It does not state when not to use the tool or name alternative tools for overlapping checks, so it stops short of full routing guidance.

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