Skip to main content
Glama

Scrutica

by io.github.davidgringras
OverviewDiscussionsAdmin

scrutica_query_export_controls

Read-only

Look up BIS Entity List designations for companies or countries. The queried dataset is the US Commerce Department Entity List, Federal-Register-anchored; it does NOT cover OFAC SDN or Wassenaar CCL (for an organization's OFAC SDN / NS-CMIC / Section-1260H status, use scrutica_get_company — the record has on_ofac_sdn / on_ns_cmic / on_1260h booleans). entity_name is a case-insensitive substring match against the designated entity's published name (no alias expansion). Returns entity_name, entity_type, country, list_type, designation_date, removal_date, grounds, federal_register_citation, source_url (Federal Register notice URL), data_quality_flags. Provide entity_name or country. entity_id filtering is not implemented: an entity_id-only call is rejected; alongside a supported filter, entity_id is ignored and the response sets entity_id_ignored: true. Authority tier: Federal-Register-anchored designations are Tier 1 (primary source). bis_coverage_class discriminates how a row is covered: explicitly_named (FR notice cites the entity by name) vs affiliate_50pct_rule (inferred via BIS's 50% Affiliates Rule). coverage_note is populated only on affiliate_50pct_rule rows and states whether that rule is currently suspended. data_quality_flags is an array of provenance/caveat notes, empty for most rows; where present (derived-country provenance, removal-date sourcing, or the affiliate rows' suspension and substrate-reproducibility caveats) treat it as load-bearing context for the row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
countryNoISO 3166-1 alpha-2
entity_idNoRetained for compatibility; filtering by this ID is not implemented. An ID-only call is rejected; with entity_name or country, the ID is ignored and entity_id_ignored is true.
entity_nameNoCase-insensitive substring of the designated entity's published name; no alias expansion. Supply entity_name or country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / entity_id / description
      Previous value: -"Scrutica org ID (exact match)"New value: +"Retained for compatibility; filtering by this ID is not implemented. An ID-only call is rejected; with entity_name or country, the ID is ignored and entity_id_ignored is true."
    • changedInput schema / properties / entity_name / description
      Previous value: -"Company name (fuzzy matched against aliases)"New value: +"Case-insensitive substring of the designated entity's published name; no alias expansion. Supply entity_name or country."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint, the description reveals matching semantics (case-insensitive substring, no alias expansion), the non-implemented entity_id filter and its response flag, output field list, authority tier, coverage class distinctions, and data_quality_flags semantics. No contradictions with 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 longer than average, but the length is earned because it must compensate for no output schema and explain output interpretation. It is front-loaded with purpose and exclusions, though it partially repeats input-schema text for entity_name and entity_id.

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?

With no output schema, it enumerates all returned fields and gives load-bearing interpretation for bis_coverage_class and data_quality_flags. It also covers dataset scope, authority tier, and the behavior of entity_id, so an agent can invoke and interpret results without further lookups.

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 already documents entity_name, entity_id, and country; the description largely restates those semantics rather than adding new parameter meaning. It adds the one-of usage rule ('Provide entity_name or country'), but limit remains self-explanatory from schema min/max/default.

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?

Opens with a specific verb and resource: 'Look up BIS Entity List designations' and immediately draws the boundary against OFAC SDN and Wassenaar CCL, naming scrutica_get_company as the alternative. This clearly separates it from all nine sibling tools.

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?

Explicitly states when not to use it ('does NOT cover OFAC SDN or Wassenaar CCL') and provides the alternative (scrutica_get_company for OFAC/NS-CMIC/1260H). It also gives the required input pattern ('Provide entity_name or country') and the entity_id caveat.

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

All Scrutica toolsInspect
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