Skip to main content
Glama
Sign In
AFAS MCP Server

AFAS MCP Server

by schubergphilis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Read rows from a GetConnector

afas_get_rows
Read-onlyIdempotent

Read one page of rows from an AFAS Profit GetConnector, applying field filters and sort order to query specific business data.

Instructions

Read one page of rows from a GetConnector, with optional filters and sort order.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "connector_id": "<connector_id>"
    },
    "name": "afas_get_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of rows to skip; combine with take to page.
takeNoRows to return; defaults to the configured page size.
filtersNoConditions on field ids. Same group = AND, different groups = OR.
order_byNoField ids to sort on, prefix with - for descending. Required for reliable paging.
connector_idYesConnector id as listed by afas_list_connectors, e.g. Profit_Employees.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds only that results are a single page and that filters and sorting are optional; it does not add much about paging behavior or result handling beyond what the annotations and schema already convey.

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?

The description is a single well-formed sentence with no wasted words. It front-loads the action and resource and efficiently mentions the main optional capabilities.

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 rich schema, full parameter descriptions, annotations, and the presence of an output schema, the description is nearly complete for an agent to call the tool correctly. It could be improved by mentioning connector and field discovery, but the core paging, filtering, and sorting purpose is covered.

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 parameters such as skip, take, filters, order_by, and connector_id are already well documented. The description only restates that filters and sort order are optional, adding no meaningful semantics 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?

The description states a specific verb and resource: 'Read one page of rows from a GetConnector,' with optional filters and sort order. It is clear what the tool does, though it does not explicitly differentiate itself from the sibling meta-tools such as afas_describe_get_connector.

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 description implies usage for reading GetConnector rows, but gives no explicit when-to-use guidance, prerequisites, or alternatives. An agent can infer it is the data-retrieval step, but must rely on other tools and the schema to understand connector discovery and field discovery.

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