Skip to main content
Glama
Sign In
io.github.resuly/daleads-mcp

io.github.resuly/daleads-mcp

by resuly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_categories

Retrieve all trade categories with record counts, such as Renovation/Extension and Swimming Pool/Spa, to filter development application searches.

Instructions

List all trade categories with record counts.

Returns categories like: Renovation / Extension, Swimming Pool / Spa, Granny Flat / Secondary Dwelling, Demolition, etc.

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": "list_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, but the description discloses that the tool returns categories with record counts and provides examples. It doesn't mention ordering, filtering, or pagination, but for a simple list operation this is acceptable. The output schema likely covers return structure.

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?

Two concise sentences, front-loaded with the purpose ('List all trade categories with record counts'), and then illustrative examples. No superfluous 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?

Given the output schema exists, the description doesn't need to explain return values. It provides enough context for a trivial zero-parameter tool, though it could mention that categories are tied to development applications, but that's implied by the sibling context.

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 input schema is empty. The baseline for 0 parameters is 4, and the description adds no parameter semantics because there are none to explain.

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 lists all trade categories with record counts, and gives concrete examples. It distinguishes itself from sibling tools like search_das or get_da, which are not about categories.

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

Usage Guidelines3/5

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

The use case is implied: call this tool when you need the list of trade categories. There is no explicit guidance on when not to use it or alternatives, but given its simplicity, the implied usage is sufficient.

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