Skip to main content
Glama

Dynomatix

by com.dynomatix

Apply for a position

dynomatix_submit_application

Submit a job application to Dynomatix, résumé included. This is final: it delivers straight to a monitored human inbox and cannot be edited, recalled or deleted afterwards. Confirm the details with the person you are acting for before you call it, and do not call it twice for the same submission — a retry sends a second copy. Set position to a slug from dynomatix_list_open_positions. Supply the résumé exactly one of two ways: resume_url, an https link that downloads the file itself (a sharing page from a drive or a document service is not a direct link and will be refused), or resume_base64 together with resume_filename. Supplying both, or neither, is refused. The résumé must be a PDF, DOC or DOCX file under 5 MB; its contents are checked against its extension, so a renamed file is refused too. Nothing is stored until every field passes, and the reply confirms receipt with a submission id worth quoting in any follow-up — it never returns the résumé or a link to it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe applicant's full name.
emailYesThe applicant's email address, in the form name@example.com. This is the only way they will be contacted, so check it before sending.
phoneNoOptional. The applicant's phone number.
letterNoOptional cover letter. Newlines are preserved.
positionYesSlug of the role, from dynomatix_list_open_positions. A role that is not on that list is not accepting applications.
portfolioNoOptional. A full web address starting with http:// or https:// — a portfolio, GitHub profile or personal site.
resume_urlNoAn https URL that downloads the résumé file directly. Not a sharing or preview page — the response must be the file itself. Use this OR resume_base64, never both. http:// is refused, as are hostnames that resolve inside a private network.
resume_base64NoThe résumé's bytes, base64-encoded. Use this OR resume_url, never both. Requires resume_filename. Payloads over 5 MB are refused before they are decoded.
resume_filenameNoRequired with resume_base64: it is the only source of the file's extension, which must be one of PDF, DOC or DOCX. Optional with resume_url, where the URL's last path segment is used instead.

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and thoroughly discloses the irreversible nature, retry duplication, strict file validation (direct link, extension-content match, size limit), conditional storage, and the submission ID in the reply. This goes well beyond a basic 'submits an application' statement.

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?

The description is long but every sentence is information-dense and necessary for a high-stakes irreversible action. It is front-loaded with the core purpose and warnings, then systematically covers parameter usage and validation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 9 parameters, no annotations, and no output schema, the description is exceptionally complete: it covers prerequisites, exact usage rules, refusal conditions, storage behavior, and the shape of the reply. The only minor omission is the absence of a stated response shape, but it says a submission id is returned.

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 100%, but the description adds meaningful cross-parameter semantics: the mutually exclusive resume_url/resume_base64 pairing, the resume_filename requirement, the direct-link requirement, and the content-extension check. These details are partly in the schema but the description synthesizes them and adds finality/submission-id behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Submit a job application to Dynomatix, résumé included.' It clearly distinguishes this from sibling tools like list_open_positions and submit_enquiry by focusing on the submission action and its irreversible delivery to a human inbox.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context: it is the final step after choosing a position from dynomatix_list_open_positions, with explicit warnings to confirm details and avoid duplicate submissions. However, it does not explicitly contrast with sibling tools like submit_enquiry or state when not to use this tool other than via the position-slug constraint.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Dynomatix toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct action and resource: about, list/get positions, list/get work, submit application/enquiry. There is no overlap; an agent can easily select the correct tool based on whether it needs company info, a job posting, a case study, or to submit a form.

Naming Consistency4/5

The dynomatix_ prefix is consistent, and most tools follow a verb_noun pattern (list_open_positions, get_position, submit_application). The exception is dynomatix_about, which uses a noun instead of a verb, but it is a single minor deviation and the overall pattern remains predictable.

Tool Count5/5

Seven tools is well-scoped for a company website that provides company info, job listings, case studies, and two submission forms. Each tool earns its place, and there is no bloat or redundancy.

Completeness5/5

For the apparent domain (Dynomatix's public site), the tool set fully covers reading about the company, browsing and retrieving jobs and work, and submitting applications and enquiries. There are no obvious dead ends: list tools feed detail tools, and submission tools have clear input requirements.

Resources