Skip to main content
Glama

Adcvd Case

adcvd_case
Read-onlyIdempotent

Look up a specific US antidumping/countervailing duty case by its case number (A-570-979 style: letter A=antidumping or C=countervailing, 3-digit country code, 3-digit case code) or by a Federal Register document number. Returns every Federal Register notice on file for that case with full abstract text and the FR URL, use after adcvd_orders when you already have the case number and need the underlying notices (initiation, order, continuation, revocation, amendments) in one place.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "case_number": "A-570-209"
    },
    "name": "adcvd_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_numberNoAD/CVD case number, e.g. "A-570-979" or "C-570-980"
document_numberNoFederal Register document number, e.g. "2026-16033" (alternative to case_number)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "case_number": "A-570-209"
      +  }
      +]
  2. Changed1 schema field changed
    • removedInput schema / examples
      Removed value: -[
      -  {
      -    "case_number": "A-570-209"
      -  }
      -]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine value beyond them by disclosing the return contents (every Federal Register notice with full abstract text and the FR URL) and by enumerating the notice types returned (initiation, order, continuation, revocation, amendments). It loses a point for not hinting at result volume or what happens on a case number with no matches.

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?

Front-loads the verb, resource and key formats, then closes with the routing rule, with no filler sentences. It is one long run-on sentence whose final clause ("...the FR URL, use after adcvd_orders...") would read better split or punctuated, slightly hurting scannability.

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?

For a two-parameter read-only lookup with no output schema, the description covers input formats, the alternative key, the return payload and the sibling relationship. The only real gap is failure behavior (no case found, ambiguous case number), which an agent would need before relying on it unattended.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns an upgrade by decoding the case-number grammar (A=antidumping, C=countervailing, 3-digit country code, 3-digit case code), which the schema only illustrates by example. It also reinforces that document_number is an alternative key rather than a required companion.

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?

States a specific verb ("Look up") and a precise resource ("a specific US antidumping/countervailing duty case"), then names the two lookup keys and the return payload. It explicitly differentiates itself from the sibling adcvd_orders by positioning itself as the downstream notice-retrieval step, so an agent can pick between them 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?

Gives clear sequencing guidance: "use after adcvd_orders when you already have the case number and need the underlying notices." This is close to an explicit when-to-use plus alternative rule. It stops short of 5 because it never states when NOT to use it (e.g., what to do when you have no case number or document number) and doesn't cover lookup-by-participant or by product.

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.