Dynomatix

List past and current work

dynomatix_list_work

List the products and client work Dynomatix has shipped. Returns one entry per item with its name, the year it started, its status, a short description and its links. Retired items are included — the site shows them and status says which is which — because a track record with the failures removed is not a track record. Where caseStudyUrl is not null, dynomatix_get_work will return the full write-up for that slug. Takes no arguments.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`work`	Yes	Products and engagements, in the order the site lists them.

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries the full transparency burden. It discloses the return format (one entry per item with specific fields), the inclusion of retired items, the role of `status`, and the behavior around `caseStudyUrl`. It also explains the reasoning for including retired items, which is valuable behavioral context beyond a simple list operation.

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 three sentences long and front-loads the core purpose. Every sentence adds value: the first defines what is listed, the second clarifies item fields and inclusion of retired work, and the third links to a complementary tool. 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?

Given the tool's low complexity (no parameters) and the presence of an output schema, the description covers all necessary ground: scope of items, what fields are returned, handling of retired items, and how to access detailed write-ups. It is fully self-contained for an agent to select and invoke correctly.

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, so the baseline is 4. The description explicitly states 'Takes no arguments,' eliminating any ambiguity. Since the schema is empty, there is no additional parameter behavior needed, and the description covers the only relevant semantic: no input is required.

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 clear, specific verb and resource: 'List the products and client work Dynomatix has shipped.' This immediately distinguishes it from sibling tools like dynomatix_list_open_positions (jobs) and dynomatix_get_work (single write-up), making the tool's purpose unambiguous.

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?

The description provides clear context by explaining that all work is listed, including retired items, and that `caseStudyUrl` links to a more detailed write-up via dynomatix_get_work. It names the alternative for detailed reads, though it does not explicitly state when NOT to use this tool, so it stops short of a full when/when-not guideline.

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?