Dynomatix

List open positions

dynomatix_list_open_positions

List every role Dynomatix is currently hiring for. Returns one entry per position with its slug, title, one-line summary, employment type, canonical URL and posting dates. Start here before dynomatix_get_position or dynomatix_submit_application: the slug this returns is the value both of them expect. An empty list means there are no openings right now, not that the lookup failed. Takes no arguments.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`positions`	Yes	Open roles, in the order the site lists them.

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses return contents (slug, title, summary, etc.), empty-list semantics (no openings vs. failure), and confirms no arguments. It doesn't discuss auth or rate limits, but for a simple read-only list tool this is sufficient transparency.

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?

Three sentences, each earning its place: purpose, return details + usage guidance, and empty-list semantics. Front-loaded with the main verb phrase. No wasted words.

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 no-param list tool with an output schema, the description covers purpose, return fields, relation to sibling tools, edge case (empty list), and argument expectations. It leaves no meaningful gaps for an agent to misuse the tool.

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?

The tool has zero parameters and the schema is an empty object. The description explicitly states 'Takes no arguments,' reinforcing the schema and eliminating any ambiguity. This adds value beyond the bare 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 opens with 'List every role Dynomatix is currently hiring for', a specific verb+resource statement. It also distinguishes itself from siblings by explicitly positioning as the entry point for get_position and submit_application, clarifying its unique role.

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?

Provides explicit when-to-use guidance: 'Start here before dynomatix_get_position or dynomatix_submit_application' and explains that the returned slug is expected by both. Also interprets empty results to avoid false negatives, giving clear context for using the tool.

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?