AFAS MCP Server

List AFAS connectors

afas_list_connectors

Read-onlyIdempotent

Lists the AFAS Profit GetConnectors and UpdateConnectors the configured token can access, optionally filtered by keyword to find connectors by ID or description.

Instructions

List the GetConnectors and UpdateConnectors the configured token may use, optionally filtered by keyword.

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

Input Schema

Name	Required	Description	Default
`kind`	No	Which connectors to list: get (read), update (write) or all.	all
`search`	No	Keep only connectors whose id or description contains this.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds a genuinely useful fact beyond them: results are limited to what the configured token is permitted to use, which explains empty or truncated listings. Return shape and pagination are not described, but an output schema exists, so that gap is acceptable.

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?

A single front-loaded sentence with no filler: the resource, the token scoping, and the optional filter all appear in one pass. Nothing is repeated and nothing needs trimming.

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 two-optional-parameter read tool with full schema coverage, an output schema, and complete annotations, the description covers what the tool returns at a high level and why results may be constrained. It would be fully complete if it positioned itself as the discovery entry point before the describe_* siblings.

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 description coverage is 100%, so both parameters are already documented (kind enum with get/update/all, search matching id or description). The description only restates the keyword filtering, which is narrower than the schema's id-or-description matching, adding no new semantics; 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?

"List the GetConnectors and UpdateConnectors the configured token may use" gives a specific verb (list) and a specific resource (connector definitions of both kinds). The verb contrast with the sibling tools afas_describe_get_connector / afas_describe_update_connector is implicit rather than stated, so it is clear but not explicitly differentiated.

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 only usage signal is "optionally filtered by keyword", which implies a discovery step but never says when to call this instead of afas_describe_get_connector or afas_connection_info. No exclusions, prerequisites, or sequencing guidance are given, so the agent must infer the browse-then-describe workflow.

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

Deploy Server