argus-face
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FACE_API_KEY | Yes | Your Face Terminal API key, sent in the X-API-Key header. | |
| FACE_API_URL | No | Overrides the base URL. Defaults to https://face.unbackoffice.com. | https://face.unbackoffice.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| face_verifyA | Check that a selfie shows the same person as an ID document or face photo, and that the selfie is a genuine capture (not a printout, screen, mask or synthetic face), via Face Terminal (POST /v1/face/verify). When the reference is a passport, ID card, residence permit or driving licence, the document is checked too. Takes local file paths (JPEG, PNG or WebP, up to 12 MB each). Returns status (verified, review or failed), reasons, the face match, the spoof check and the document check. Uses one check from the key's quota. You need a lawful basis, usually the person's explicit consent, to send their face. A result supports a human decision. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between tools. Its purpose (1:1 face/document verification with liveness and spoof detection) is stated unambiguously in the description.
The single name face_verify is snake_case and descriptive, so there is no inconsistency to speak of. It is noun-first rather than the common verb_noun convention, but with one tool no pattern is broken.
The server wraps what appears to be a single Face Terminal verification endpoint, so one tool is defensible, but the surface is thin. There are no adjacent tools such as checking API/quota status or retrieving prior verification results, which would be reasonable companion operations.
The one tool covers the full verification lifecycle in a single call: status, reasons, face match, spoof check and document check, with clear input constraints (file paths, formats, size). Minor gaps remain, such as no way to query remaining quota or fetch historical/async results.