Skip to main content
Glama
Sign In

AgentX

by com.agentxhq
OverviewDiscussionsAdmin

list_artifacts

Read-onlyIdempotent

List files the agents have produced and published — reports, diagrams, build output. Omit limit for 100 files; pass 0 for the full set. Use next_cursor as cursor to continue, or query to filter by agent name or relative path. Name an agent to see only its files, or leave empty to see everything you can reach.

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

Input Schema

NameRequiredDescriptionDefault
toNoSame as agent. agent wins when both are set.
agentNoShow only this agent's files. Leave empty to list everything you can reach.
limitNoMost files to return. Omit for 100. Explicit 0 returns the full set.
queryNoFilter by agent name or relative path.
cursorNoOpaque next_cursor returned by the previous list_artifacts page.
session_idNoShow files from one exact session. Only use this when you already have a session id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the 100-item default, the unbounded explicit-0 case, and the pagination continuation loop via next_cursor. It doesn't note ordering of results, which is a minor omission.

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 what is listed and the example artifact types, then pagination and filtering. The final sentence ("Name an agent to see only its files, or leave empty to see everything you can reach") largely duplicates the earlier query/agent guidance and the schema's own wording, a small amount of waste.

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 six-parameter, all-optional list tool with rich annotations and no output schema, the description covers scoping, filtering, and pagination adequately. It does not describe the shape of returned items beyond the next_cursor mention, but the annotations and schema leave little ambiguity about how to call it.

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 coverage is 100%, so the schema already documents every parameter including the agent/to alias precedence. The description restates limit, query, and agent semantics and adds only the next_cursor-to-cursor mapping, leaving `to` and `session_id` unmentioned. Baseline 3 is appropriate when the schema carries the detail.

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 files the agents have produced and published") and grounds it with concrete examples (reports, diagrams, build output). The list-vs-get distinction from the sibling get_artifact is implicit in the verb rather than called out explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operational guidance for the parameters: default of 100 when limit is omitted, 0 for the full set, cursor for continuation, query for filtering, and agent for scoping. It does not say when to prefer this over get_artifact or check_agent_output, so it stops short of full alternative routing.

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

All AgentX 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