bewerbungsfoto-check-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANALYSIS_MODE | No | Optional analysis mode. Defaults to auto. Set to 'full' to exercise the diagnostic full decoder locally via wrangler --var ANALYSIS_MODE:full. | auto |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Technical checks only. Results describe checked coverage and limitations.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_headshot_photoA | Use this when the user wants technical checks of one professional profile or job-application photo from a public HTTPS URL or base64. Maximum 8 MB; image_url is recommended. Base64 above roughly 150 KB may exceed the Worker CPU budget. Auto mode resizes through an optional Images binding for pixel metrics, including WebP. Without it, only small JPEG/PNG inputs receive pixel checks; other inputs receive explicit header-only results. Sharpness detects coarse blur only. Face framing is not checked. URL fetching contacts user-selected external hosts and is limited to 8 seconds and 3 redirects. Cloudflare Images may internally resize the input for metrics; no edited image is returned. Operational call metadata is logged. Do not use for image creation, editing, personal-attribute judgments or identity verification. The image is analysed in memory and not stored. It does not generate images, video or audio or return edited images. It does not judge attractiveness, identity, age, gender, ethnicity or any other personal attribute; no face recognition or biometric identification. |
| get_headshot_photo_requirementsA | Use this when the user wants a technical headshot checklist and crop recommendations for LinkedIn, XING or job applications. Returns static recommendations, not official platform upload limits; no image input or external network access. No persistent changes; operational call metadata is logged. Do not use for assessing an actual image or confirming platform acceptance. The image is analysed in memory and not stored. It does not generate images, video or audio or return edited images. It does not judge attractiveness, identity, age, gender, ethnicity or any other personal attribute; no face recognition or biometric identification. |
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 2 tools
One tool analyzes an actual image, the other returns a static checklist, and each description explicitly rules out the other's use case ('Do not use for assessing an actual image'). There is no resource or action overlap, so misselection is essentially impossible.
Both names use snake_case with a verb prefix and the shared core noun 'headshot_photo' (check_headshot_photo, get_headshot_photo_requirements), which is predictable. The second name is noticeably longer and mixes an action verb with a noun-phrase suffix, but the pattern is still readable.
Two tools is thin for a server surface, though the underlying domain (analyzing one photo plus returning static guidance) is genuinely narrow. It sits at the borderline where the pairing covers the basics but leaves little room for anything else.
The pair covers the core loop: get a technical checklist, then check a real image against expectations, with clear documented limits (size, URL fetch, no face framing check). Gaps exist — no combined 'analyze and recommend fixes' output, no batch or multi-platform validation — but agents can work around them by combining the two tools.