Skip to main content
Glama
Sign In

AIAgentCycle

by com.aiagentcycle
OverviewDiscussionsAdmin

Systems AIAgentCycle integrates

list_integrations
Read-onlyIdempotent

The integrations catalogue of aiagentcycle.com (190 systems): name, status, domain, category, description, open-source license and a detail-page url where one exists. Status: productie = already running in production at AIAgentCycle or a client; standaard = n8n has a built-in node; maatwerk = custom via API, export, database or screen automation. Filters: query (name or text, max 100 chars), domain (administratie, verkoop, samenwerken, data), status, open_source. lang is nl or en. A system that is not listed can usually still be connected through one of those four routes.

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the content: nl (Dutch, the primary site language) or en (English).nl
queryNoOptional words that must all occur in the name, description, category or license, for example 'twinfield' or 'crm'. Max 100 characters.
domainNoOptional domain filter: administratie (finance and admin), verkoop (customers and sales), samenwerken (work and communication) or data (data, servers and AI).
statusNoOptional status filter: productie (running in production), standaard (n8n built-in node) or maatwerk (custom).
open_sourceNotrue for only open-source systems, false for only proprietary ones; leave out for both.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"Optional domain filter: administratie (finance and admin), verkoop (customers and sales), samenwerken (work and communication) or data (data, servers and AI)."
    • addedInput schema / properties / domain / enum
      Added value: +[
+  "",
+  "administratie",
+  "verkoop",
+  "samenwerken",
+  "data"
+]
    • addedInput schema / properties / lang / description
      Added value: +"Language of the content: nl (Dutch, the primary site language) or en (English)."
    • addedInput schema / properties / lang / enum
      Added value: +[
+  "nl",
+  "en"
+]
    • addedInput schema / properties / open_source / description
      Added value: +"true for only open-source systems, false for only proprietary ones; leave out for both."
    • addedInput schema / properties / query / description
      Added value: +"Optional words that must all occur in the name, description, category or license, for example 'twinfield' or 'crm'. Max 100 characters."
    • addedInput schema / properties / status / description
      Added value: +"Optional status filter: productie (running in production), standaard (n8n built-in node) or maatwerk (custom)."
    • addedInput schema / properties / status / enum
      Added value: +[
+  "",
+  "productie",
+  "standaard",
+  "maatwerk"
+]
  2. First observed

TDQS

A3.9/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 non-open-world, so safety is covered. The description adds real behavioral context beyond that: it discloses the corpus size (200 systems, here 190), defines the three coverage statuses (productie = live in production, productie vs. standaard/mass-produced), and states the limits of the catalogue ('if it is not listed, it can probably still be integrated via one of four approaches'), which sets expectations about coverage gaps.

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?

Front-loaded with identity and corpus size, then value definitions, then filters — a sensible ordering. It is somewhat dense and restates enum glosses that also live in the schema, but there is no filler or marketing language.

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?

With an output schema present and 100% parameter coverage, the description need only supply scope and the meaning of the domain-specific status values, both of which it does. The one omission is what happens when no integration matches or whether results are paged/limited, which is not disclosed.

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% and three of the five parameters are enums, so the schema already carries the semantics. The description's filter glosses (domain, status, query max 100 chars) largely duplicate the schema text rather than adding syntax rules, ordering behavior, or defaults not already stated.

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?

Opens with a specific verb+resource ('The integrations catalogue of aiagentcycle.com (190 systems)') and enumerates the fields returned, so the agent immediately knows this is a filterable list of third-party system integrations. It is clearly distinct from every sibling, which deals with contacts, services, cases, documents and knowledge-base content rather than integration systems.

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 enumerates the available filters (domain, status, category) and the meaning of each status value, which implies how to narrow a search, and adds the useful note that non-listed systems can usually still be integrated. However, it never states when to reach for this tool versus a sibling lookup or what happens when the name search returns nothing, so usage is implied rather than prescribed.

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

All AIAgentCycle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources