Scrutica

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, entity / addition / removal counts, 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 entity_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). The event date is derived (modal designation_date, falling back to modal effective_date) and labeled with its source.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max 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.
`weeks`	No	ISO-week span of the activity rollup (default 8 — the change-log page's own window; max 52).
`company_id`	No	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.

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses bounded results, the 24-event cap, truncation in metadata, separate date-keyed removal events, zero-count week semantics, and the derivation of event dates with authority tier. These are exactly the non-obvious behaviors an agent needs to interpret results correctly.

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

Conciseness5/5

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

The description is long but proportionally so for a complex tool; it front-loads purpose and routing, organizes return semantics into labeled paragraphs, and every sentence carries operational meaning. No filler is present.

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, the description carries the burden of explaining return values, and it does: event composition, counts, samples, rollup, truncation, and removal handling. It also clarifies zero-count weeks and authority sourcing, so an agent has enough context to call and interpret the tool 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 still adds value by explaining that 'count field always reports the full total in scope,' that truncation appears in metadata, and that company_id only matches entities in the cross-reference id space — avoiding false scoping assumptions.

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?

The first sentence defines a specific operation and resource: 'What CHANGED in the BIS Entity List, as bounded change-log summaries.' It also names the sibling it competes with (scrutica_query_export_controls) and the freshness scenario, so an agent can tell them apart without opening schemas.

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?

The description gives explicit routing: 'PREFER this over scrutica_query_export_controls for freshness questions' and 'Do NOT use this to look up one entity's designation rows — use scrutica_query_export_controls.' It also scopes company_id to an already-resolved organization, clarifying when the parameter is appropriate.

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

All Scrutica tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a clearly distinct resource or action: canonical entity/facility/program lookups, free-text search, supply-chain traversal, BIS query versus BIS change-log, FLOP estimation, and methodology docs. Cross-references explicitly redirect likely-confused intents, such as using scrutica_query_export_controls for entity designations and scrutica_entity_list_changes for changes, so misselection is unlikely.

Naming Consistency4/5

The naming is mostly consistent: scrutica_get_* for canonical lookups, plus clear action-style names like scrutica_search, scrutica_query_export_controls, and scrutica_estimate_flops. The main deviation is scrutica_entity_list_changes, which reads as a noun phrase rather than a verb-first tool name, so the pattern is coherent but not perfectly uniform.

Tool Count5/5

Ten tools is well calibrated for this server's broad but focused domain coverage. Each meaningful data area gets one or two dedicated tools—companies, facilities, sovereign programs, supply chain, export controls, scenarios, methodology, and FLOP estimation—with no count-inflating duplicates.

Completeness4/5

The read-side surface is largely complete: search, get-by-ID, change-tracking, relationship traversal, scenario retrieval, and methodology lookup all exist. The main gap is that some methodology topics describe metrics or indices—such as cost-index and compute-visibility index—without an obvious dedicated tool for retrieving those metric values directly.

Resources

Need Help?