Skip to main content
Glama
Sign In
Tradify MCP

Tradify MCP

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tradify_read

Read the current Tradify page text and numbered buttons, links, and fields, optionally scoped to one element, so an AI agent can inspect and interact with the signed-in account.

Instructions

Read the current Tradify page: its text and numbered buttons, links and fields.

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_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the return payload (page text plus numbered buttons, links, fields), which is genuinely useful behavior beyond a bare name. It says nothing about whether the read has side effects, whether it fails when no page is loaded, or how much content is returned, leaving meaningful gaps for an unannotated tool.

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?

A single front-loaded sentence with the verb and resource first, followed by a compact colon list of returned artifacts; no filler. It could be slightly better structured by separating the usage hint (numbering) from the content list.

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

Completeness3/5

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

For a simple one-optional-param read tool with no output schema or annotations, the description covers what is returned, which is the core need. It omits the precondition of an open page and any note that the numbered elements are the handles other tools consume, both of which an agent would need to sequence calls correctly.

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?

The single optional parameter is fully documented in the schema ("Read only inside this element") at 100% coverage, so the baseline of 3 applies. The description does not mention the scoping parameter at all, adding no meaning beyond the schema.

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?

"Read the current Tradify page" names a specific verb and resource, and the colon list (text, numbered buttons, links, fields) states exactly what comes back. The verb "read" also implicitly separates it from the act-oriented siblings (tradify_click, tradify_type, tradify_open), though none is named explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of alternatives, and no stated prerequisite such as a page being open via tradify_open. At most, "numbered" hints that the returned indices feed into tradify_click, but that is left entirely to inference.

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

Deploy Server

Other Tools