Skip to main content
Glama
Selerity

accelo-mcp

by Selerity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

accelo_list_contacts

Retrieve and filter Accelo contacts by email, name, status, or date to find specific client records. Search, paginate, and select fields to build contact lists.

Instructions

List contacts from Accelo.

Args: filters: Filter dict. Keys: id, email, title, standing, affiliation, status, username, contact_number, date_created/modified_before/after, order_by_asc/desc (id, fullname, firstname, surname, date_modified, etc.) fields: Additional fields, e.g. "default_affiliation(),comments" search: Search over firstname, surname, email page: Page number (0-indexed) limit: Results per page (max 100)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
limitNo
fieldsNo
searchNo
filtersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are present, so the description must carry behavioral disclosure. 'List' implies a read-only operation and it specifies page is 0-indexed and limit max 100, but it omits auth requirements, rate limits, and return behavior.

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?

Purpose is front-loaded in one sentence, followed by a compact Args block. Every line adds parameter information, and there is no redundant prose.

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?

The description covers the callable parameters but does not address return structure, pagination totals, auth requirements, or when to prefer count/get siblings. For a list endpoint with no output schema and no annotations, it is adequate but incomplete.

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?

Schema description coverage is 0%, so the description must compensate. It documents all five parameters, including filter keys, searchable fields, fields example, page indexing, and limit cap; only value formats for filters are not fully specified.

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?

States a specific verb and resource: 'List contacts from Accelo.' It is clear what the tool returns, but it does not differentiate from siblings like accelo_count_contacts or accelo_get_contact.

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?

No when-to-use guidance or alternatives are provided. The description only enumerates arguments, leaving the agent to infer that this is the bulk-retrieval tool rather than count/get.

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