Tradify MCP

tradify_guide

Explains how to work in Tradify: create jobs, quotes and invoices, book staff, find screens and get the sign-in link. Call it first for plain-language guidance.

Instructions

How to work in Tradify (create jobs, quotes and invoices and book staff): its screens and the sign-in link. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tradify_guide"
  }
}

Input Schema

Name	Required	Description	Default
`task`	No	What you want done in Tradify, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the burden of disclosure. It usefully signals the return content (screens and a sign-in link) and that this is orientation material rather than an action, but it says nothing about whether the guidance is static documentation, how current it is, or how large the response is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with what the guide covers and ending with the actionable ordering cue. The parenthetical list is slightly dense but every clause carries information.

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

Completeness4/5

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

For a low-risk, single-parameter orientation tool with no annotations or output schema, the description covers what the guide contains, what workflows it supports, and when to call it. The only real gap is not explaining what the returned guidance looks like or how to use the task parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single 'task' parameter is documented in-schema as free-form wording. The description never mentions the parameter or how to phrase the task, so it adds no meaning beyond the schema; baseline 3 applies.

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

Purpose4/5

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

The description names the resource (Tradify) and the content of the guide: screens, the sign-in link, and workflows for creating jobs, quotes, invoices and booking staff. That is specific enough to distinguish it from the action siblings (click, open, read, status), though that differentiation rests only on the generic 'Call this first' rather than naming what those tools do.

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?

'Call this first' is explicit sequencing guidance that tells the agent to consult this tool before invoking the operation siblings. It gives no when-not conditions or named alternatives, which keeps it short of a 5.

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

Deploy Server