OTP/OJP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| otp_validate_profileA | Validate a JSON document against the Open Talent Protocol schema (v0.1). Provide either filePath (absolute path to a .json file) or document (pre-parsed object). Returns validity status and a list of errors. |
| otp_introspect_profile | Extract a structured, agent-friendly summary of an Open Talent Protocol document. Returns normalized skills, work history, preferences, and an agentSummary string suitable for use in a system prompt. Provide either filePath or document. Optionally filter sections: identity, summary, skills, work, preferences. |
| otp_parse_resumeA | Produce a structured OTP extraction template from raw resume text. Returns a document skeleton with EXTRACT* annotations, a fieldConfidence list (high/medium/low per field), and a gaps list of information not typically on resumes. The calling agent should fill in the skeleton using its reasoning over the text, then call otp_validate_profile to verify the result. |
| ojp_validate_job_postingA | Validate a JSON document against the Open Job Protocol schema (v0.1). Provide either filePath (absolute path to a .json file) or document (pre-parsed object). Returns validity status and a list of errors. |
| ojp_introspect_job_postingA | Extract a structured, agent-friendly summary of an Open Job Protocol document. Returns normalized requirements, compensation, location, team, process details, and an agentSummary string suitable for use in a system prompt. Provide either filePath or document. |
| ojp_parse_job_postingA | Produce a structured OJP extraction template from raw job posting text. Returns a document skeleton with EXTRACT* annotations, a fieldConfidence list (high/medium/low per field), and a gaps list of information commonly missing from postings. The calling agent should fill in the skeleton using its reasoning over the text, then call ojp_validate_job_posting to verify the result. |
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 5 tools
Each tool has a distinct purpose clearly indicated by the name: OTP vs OJP, then validate, parse, or introspect. No two tools overlap in function.
All tools follow a consistent pattern of 'protocol_action_target' in snake_case, e.g., otp_validate_profile, ojp_parse_job_posting. No deviations.
5 tools cover two protocols (OTP and OJP) with essential operations: validation, parsing, and introspection (for OJP). The count feels well-scoped for the domain.
The set covers validation and parsing for both protocols, plus introspection for OJP. A minor gap is the lack of an introspection tool for OTP, but the stated purpose is sufficiently served.