Skip to main content
Glama
Sign In

screening

by com.compliapi
OverviewDiscussionsAdmin

Screen an aircraft

screen_aircraft
Read-only

Screen an aircraft by registration (tail number, e.g. EP-GOL), manufacturer's serial number or Mode S transponder code (OFAC SDN publishes these). Exact match, ignoring punctuation and case; serial numbers under six characters are not indexed. Each match carries the aircraft model. lists: optional comma-separated list slugs.

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": {
      "identifier": "<identifier>"
    },
    "name": "screen_aircraft"
  }
}

Input Schema

NameRequiredDescriptionDefault
listsNo
identifierYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world safety, and the description adds genuinely new behavior: exact-match semantics, punctuation/case normalization, the six-character serial-number indexing floor, and the fact that matches carry the aircraft model. It stops short of saying what an empty result means or which lists are covered by default.

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?

Three compact sentences, front-loaded with the action and accepted identifiers, then the matching rules, then the optional parameter. No filler or repetition of structured fields.

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 an output schema present, return values need no explanation, and the description covers input formats and matching behavior well. What is missing is the scope of the underlying dataset (only OFAC SDN is mentioned) and any note on no-match results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden and largely meets it: it defines the accepted formats for `identifier`, its normalization rules, and one hard constraint (serials under six characters are not indexed), plus the meaning and format of `lists`. It does not enumerate valid list slugs, which is the only remaining gap.

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 and resource ('Screen an aircraft') and immediately names the three accepted identifier types, so the agent can distinguish it from siblings like screen_vessel or screen_name without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the identifier formats given (registration, MSN, Mode S) and the reference to OFAC SDN, but there is no explicit statement of when to prefer this tool over a sibling screener or what to do when the identifier type is ambiguous.

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

All screening 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