Skip to main content
Glama
Sign In

AIAgentCycle

by com.aiagentcycle
OverviewDiscussionsAdmin

List AIAgentCycle pages

list_documents
Read-onlyIdempotent

Catalogue of the website: id, type, title, url, last-modified date and a one-line summary per document. lang is nl or en. type optionally narrows to: article, page, integration, case, solution, sector.

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the content: nl (Dutch, the primary site language) or en (English).nl
typeNoOptional filter on document type: article, page, integration, case, solution or sector. Leave empty for all types.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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 / type / description
      Added value: +"Optional filter on document type: article, page, integration, case, solution or sector. Leave empty for all types."
    • addedInput schema / properties / type / enum
      Added value: +[
+  "",
+  "article",
+  "page",
+  "integration",
+  "case",
+  "solution",
+  "sector"
+]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the shape of each returned document, which is real context, but it says nothing about result volume, truncation or pagination – relevant for a whole-site catalogue – and an output schema already exists.

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?

Two sentences, front-loaded with what the tool returns, followed by the filter options. Slightly dense phrasing ('Catalogue of the website') but no filler sentences.

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?

With only two optional parameters, an existing output schema and full safety annotations, the description is close to sufficient. Missing pieces are sibling routing and any indication of catalogue size/limits, which matter for an agent deciding between this and the type-specific list tools.

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 both parameters are enum-typed with defaults documented. The description's 'lang is nl or en' and 'type optionally narrows to: article, page, ...' merely restate the schema enums and add no new meaning.

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 makes clear this enumerates site documents and enumerates the returned fields (id, type, title, url, last-modified, summary), so an agent knows it is a full catalogue rather than a single-record fetch. It is weakened only by not stating that it spans all document types (article, page, integration, case, solution, sector) and therefore differs from the type-specific siblings list_cases/list_integrations/list_services.

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?

There is no explicit when-to-use or when-not guidance and no mention of alternatives such as list_cases, list_integrations, list_services, search_knowledge_base or get_document. The only implied usage is that the type filter narrows results, which a reader must infer.

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