Skip to main content
Glama

scrutica_entity_list_changes

Read-only

What CHANGED in the BIS Entity List, as bounded change-log summaries. Backed by the same derivation the public /export-controls/changes page and its RSS feed render. PREFER this over scrutica_query_export_controls for freshness questions ("what changed this month", "latest additions", "recent removals"): designation rows arrive already grouped into per-Federal-Register-notice change events, so you do not re-derive notice grouping from citation strings. Each event includes: canonical FR citation and link, notice title / publication date / document number where the citation resolved to one FR document, a derived event date labeled with the source column it came from, entry / entity / address / removal counts (entry_count counts entries as the Register does: an entity under two destinations is two entries), per-country counts, a bounded sample of entity names, and the entities cross-referenced to compute-infrastructure organizations. Removal actions are returned separately as date-keyed events — a screening list maintained from additions alone over-blocks forever. Also returns a last-N-ISO-week activity rollup counting BOTH additions and removals. Zero-count weeks are a real quiet-Federal-Register signal, not missing data. Results are bounded summaries, never row dumps: at most 24 events per call (default 6, newest first), with any truncation declared in metadata. Cite totals from the count field and per-event entry_count, never by summing a sampled list. Do NOT use this to look up one entity's designation rows — use scrutica_query_export_controls (substring match on the published name). Use company_id here only to scope the log to notices touching an organization you already resolved. Authority tier: Federal-Register-anchored designations are Tier 1 (primary source). Each entry is dated by the effective date of the Federal Register notice that added it, the notice the Entity List's own eCFR citations for the entry resolve to (a removed record: the notice its entry was dated by while the Register printed it, else its own citation's notice), except where no citation resolves to a notice; the event date is derived (modal designation_date, falling back to modal effective_date) and labeled with its source.

Input Schema

NameRequiredDescriptionDefault
limitNoMax change events to return (default 6, max 24), newest first. The count field always reports the full total in scope. At the Federal Register's Entity-List cadence the default already reaches back several months.
weeksNoISO-week span of the activity rollup (default 8 — the change-log page's own window; max 52).
company_idNoScope to change events touching one organization. Canonical Scrutica org ID ('org-<slug>'); the id space is the matched_org_id values in the BIS cross-reference, so designated entities without a compute-substrate cross-reference never appear under a scope. Kept events retain their full entity context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / company_id / description
      Previous value: -"Scope to change events touching one organization. Canonical Scrutica org ID ('org-<slug>'); the id space is the matched_org_id values the BIS cross-reference carries, so designated entities without a compute-substrate cross-reference never appear under a scope. Kept events retain their full entity context."New value: +"Scope to change events touching one organization. Canonical Scrutica org ID ('org-<slug>'); the id space is the matched_org_id values in the BIS cross-reference, so designated entities without a compute-substrate cross-reference never appear under a scope. Kept events retain their full entity context."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true/title, so the description carries the rest and does: hard bounds (24 events max, default 6, newest first), truncation declared in metadata, removal actions returned as separate date-keyed events, zero-count weeks as a real signal rather than missing data, and authority tiering for FR-anchored designations. It even warns against the specific misuse of summing a sampled list to get totals.

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-loaded with the one-line purpose, then routing, then return contents, then bounds, then authority tier — a sensible order with each block doing distinct work. The final paragraph on notice-dating derivation is dense and partly methodology that could live behind scrutica_get_methodology, costing it a point.

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?

No output schema exists, yet the description enumerates the returned fields (canonical FR citation and link, notice title/date/document number, derived event date with source column, entry/entity/address/removal counts, per-country counts, sampled entity names, compute-infrastructure cross-references) plus the ISO-week rollup. For a bounded-summary tool this is as complete as an agent needs to call it and interpret the result 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?

Schema coverage is 100%, so the baseline is 3; the description adds guidance beyond the schema by telling the agent to scope only to organizations already resolved and noting that unmatched entities never surface under a scope. The company_id caveats largely restate the schema's own id-space note, and limit/weeks semantics are covered in the schema, so this is useful reinforcement rather than new parameter knowledge.

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+resource+output shape: 'What CHANGED in the BIS Entity List, as bounded change-log summaries,' and pins it to a known public artifact ('the same derivation the public /export-controls/changes page and its RSS feed render'). It is immediately distinguishable from scrutica_query_export_controls, which is named as the wrong tool for this job.

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?

Explicit routing both ways: 'PREFER this over scrutica_query_export_controls for freshness questions ("what changed this month", "latest additions", "recent removals")' and 'Do NOT use this to look up one entity's designation rows — use scrutica_query_export_controls.' It also constrains company_id to orgs 'you already resolved,' giving an ordering prerequisite, not just an alternative.

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