iLook Face Analysis
Server Details
Analyze user-submitted face photos with a complete report or 13 focused face-analysis tools.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.7/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion with other tools. The purpose of score_face is clear and distinct.
With a single tool, there is no pattern to evaluate. The name score_face uses a plausible verb_noun format, but consistency cannot be determined.
A single tool for a domain called 'Face Analysis' feels too thin. One would expect at least a few tools for different face analysis operations (e.g., detect_faces, compare_faces, analyze_expression).
The tool set is severely incomplete for the stated purpose of face analysis. Only a single scoring/description tool is provided, with no means to detect faces, compare faces, get landmarks, or perform other common face analysis tasks.
Available Tools
1 toolscore_faceScore an authorized adult faceAInspect
Returns descriptive face-shape context plus five subjective appearance scores for one authorized adult photo.
| Name | Required | Description | Default |
|---|---|---|---|
| mime_type | Yes | ||
| image_base64 | Yes | Base64-encoded JPEG, PNG, or WebP bytes, without a data URL prefix. | |
| adult_and_authorized | Yes | Confirms the pictured person is an adult and the submission is lawful. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full transparency burden. It states the output includes 'descriptive face-shape context' and 'five subjective appearance scores', which is useful but vague. No mention of potential biases, privacy handling, latency, or failure modes (e.g., poor lighting). Does not contradict annotations as there are none.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One clear, front-loaded sentence that conveys purpose and output. No filler or redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of an output schema, the description adequately specifies the return type: face-shape context and five scores. However, for a tool with no sibling context and no annotations, more detail about the nature of the scores (e.g., scale, categories) would improve completeness. Still, the description covers the essential functional contract.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 67% with 3 parameters. The description references 'one authorized adult photo' which aligns with the boolean constraint on 'adult_and_authorized', adding meaning beyond the schema description. The 'mime_type' enum is well-defined in schema, but the description does not clarify the 'image_base64' format beyond base64, which the schema already covers.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb 'Returns' and resource 'face-shape context plus five subjective appearance scores for one authorized adult photo'. It clearly distinguishes the tool's function, though no sibling tools exist for comparison.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for scoring an authorized adult photo, but does not provide when-not-to-use guidance or alternatives. The 'authorized adult' constraint is stated, but context about scenarios (e.g., when to use this vs other face tools) is absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityBmaintenanceExtracts deterministic facial features from photos locally using MediaPipe, returning structured JSON with measurements like face shape ratios and symmetry.MIT
- Flicense-qualityFmaintenanceProvides AI-based skin analysis from selfie image URLs, returning comprehensive skin status, personalized management recommendations, and therapy guidance including skin type classification, detailed condition scores, and treatment suggestions.
- Alicense-qualityAmaintenanceEnables face keypoint detection, beautification, age/gender transform, face swap, cartoonization, and liveness detection via AceDataCloud API.MIT
- Alicense-qualityDmaintenanceEnables face detection and recognition in Agentic AI workflows using Azure Face API, supporting attribute detection, image comparison, and face recognition.9MIT