Skip to main content
Glama

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.

MCP client
Glama
MCP server

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.

100% free. Your data is private.
Tool DescriptionsA

Average 3.7/5 across 1 of 1 tools scored.

Server CoherenceC
Disambiguation5/5

With only one tool, there is no possibility of confusion with other tools. The purpose of score_face is clear and distinct.

Naming Consistency3/5

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.

Tool Count2/5

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).

Completeness1/5

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 tool
score_faceScore an authorized adult faceAInspect

Returns descriptive face-shape context plus five subjective appearance scores for one authorized adult photo.

ParametersJSON Schema
NameRequiredDescriptionDefault
mime_typeYes
image_base64YesBase64-encoded JPEG, PNG, or WebP bytes, without a data URL prefix.
adult_and_authorizedYesConfirms the pictured person is an adult and the submission is lawful.
Behavior3/5

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.

Conciseness5/5

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.

Completeness4/5

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.

Parameters4/5

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.

Purpose4/5

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.

Usage Guidelines3/5

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.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Servers

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources