Dynomatix

Read a job posting

dynomatix_get_position

Read one job posting in full: responsibilities, requirements and how the role is set up. Returns the posting's own markdown, frontmatter included — the title and canonical URL it opens with are the citation to quote when you tell someone about the role. Call dynomatix_list_open_positions first to get a valid slug; a slug that is not currently open is refused rather than guessed at.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The position's slug, exactly as dynomatix_list_open_positions returned it. Lowercase letters, digits and hyphens.

TDQS

A4.9/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 burden. It discloses the return format (markdown with frontmatter), the role of title/canonical URL as citations, and the refusal behavior for invalid slugs. This goes beyond basic expectations.

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 concise, front-loaded with the main purpose, and each sentence provides essential information. No filler or redundancy.

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?

For a single-parameter read tool with no output schema, the description adequately explains what is returned, how to get the parameter, and error behavior. It is complete for an agent to invoke safely and effectively.

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% and the slug parameter has a detailed description. The tool description adds the important context that the slug must come from dynomatix_list_open_positions, reinforcing how to obtain it correctly. This adds value beyond the schema.

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 clearly states the tool reads one job posting in full, listing the content (responsibilities, requirements, setup). It distinguishes itself from sibling tools like dynomatix_list_open_positions (list vs. get) by specifying it reads a single posting.

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

Usage Guidelines5/5

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

Explicitly instructs to call dynomatix_list_open_positions first to obtain a valid slug, and warns that non-open slugs are refused rather than guessed. This provides clear usage context and differentiates from alternatives.

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

All Dynomatix tools Inspect

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

Need Help?