Skip to main content
Glama

IMS registration

ims_registration
Read-onlyIdempotent

Determines whether each UE is registered on IMS and explains registration failures, helping diagnose why a UE cannot register or whether it is registered for SMS or voice.

Instructions

IMS registration per UE: whether each UE is registered on IMS and, if not, why. Use it for "why can't this UE register" or "is it registered for SMS/voice"; for calls use sip_dialogs, for SMS over IMS sms_over_ims. Built from every SIP REGISTER transaction in the capture (public identity in the To header); the legs of one REGISTER through the CSCFs (same Call-ID and CSeq) count once, copies of a packet are told apart from retransmissions. Each row has the REGISTER transactions, Contact feature tags (smsip, MMTel), implicit IMPUs, third-party REGISTERs and a verdict (registered, expired, deregistered, challenge-loop, failed, in_progress, unknown) with reasons. impu keeps users whose IMPU, IMPI or P-Associated-URI contain it; imsi keeps IMSI-based identities; filter is ANDed with the REGISTER filter. More detail: resource schema://tools/ims_registration.

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": {
      "path": "<path>"
    },
    "name": "ims_registration"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoSame forms as start
impuNoIMS public identity (sip: or tel: URI, or part of it)
imsiNoIMSI, 6 to 15 digits
pathYesCapture file (absolute, in an allowed dir) or open_capture handle
limitNoMost rows per page
startNoISO 8601, epoch s, +Ns from start, -Ns from end
filterNoExtra display filter, ANDed
offsetNoRows to skip (next_offset)
outputNosummary: all but rows, plus 3 rows (<8 KB)rows
redactNoReplace subscriber identifiers in this result with tokens; ids+ips hides every IP toooff
columnsNoRow keys to keep (frame keys stay)
esp_nullNoRead SIP in NULL-encrypted ESP
max_output_kbNoLower output cap, KB

Output Schema

NameRequiredDescriptionDefault
countNo
errorNo
ipsecNokeys: esp_packets, spis, decoded_null, unreadable, esp_null, hint
offsetNo
windowNo
droppedNo
summaryNo
has_moreNo
returnedNo
capture_endNo
next_offsetNo
total_foundNo
registrationsNorows with keys: impu, impi, first_time, first_frame, last_time, verdict, reasons, registered_until, time_to_register_ms, user_agent, contact, feature_tags, smsip, mmtel, sec_agree, associated_uris, service_route, path_header, counts, transactions, third_party, reg_event_notifies, reg_subscriptions
total_matchedNo
packets_matchedNo
packets_scannedNo
total_is_lower_boundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds substantial non-obvious context: rows are derived from every SIP REGISTER, CSCF legs sharing Call-ID/CSeq are collapsed, retransmissions are distinguished from packet copies, and the complete verdict taxonomy (registered, expired, deregistered, challenge-loop, failed, in_progress, unknown) is spelled out. It does not discuss cost/limits on large captures, which is the only remaining gap.

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 outcome, then use cases, then alternatives, then derivation, then row contents, then the filter semantics and a resource link. Dense but well ordered; the deduplication/retransmission parenthetical is the one detail an agent rarely needs for selection, but it is short.

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?

For a 13-parameter analytical tool with an output schema, the description covers selection, filtering semantics, deduplication behavior and row shape, and points to resource schema://tools/ims_registration for depth. Return values need no explanation because an output schema exists.

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?

With 100% schema coverage the baseline is 3, and the description earns more by explaining matching semantics that the schema does not: impu matches IMPU, IMPI or P-Associated-URI substrings, imsi restricts to IMSI-based identities, and filter is ANDed with the REGISTER filter. start/end/offset/redact/output are left entirely to the schema, which is acceptable given full coverage.

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-plus-resource outcome: reports per-UE IMS registration status and, when not registered, the reason. It immediately differentiates from siblings by naming sip_dialogs for calls and sms_over_ims for SMS over IMS, so an agent can choose without opening a schema.

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?

Gives explicit trigger questions ("why can't this UE register", "is it registered for SMS/voice") and explicitly routes the excluded use cases to the correct alternative tools. Nothing about when this tool is the wrong choice is left to inference.

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