gapify-mcp-server

Agents: List Agents in Account

gapify_list_agents

Read-onlyIdempotent

List all agents in a specified Gapify account using its account ID to support team assignment and agent lookup.

Instructions

List all agents in the account [Agents] GET /api/v1/accounts/{account_id}/agents Auth: User API key (header api-access-token). Text values may be written in Persian (Farsi) or any other language and are sent unchanged; IDs, numbers and phone numbers may use Persian or Arabic-Indic digits.

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": {
      "account_id": "<account_id>"
    },
    "name": "gapify_list_agents"
  }
}

Input Schema

Name	Required	Description	Default
`account_id`	Yes	The numeric ID of the account

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 20, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description earns credit by adding the concrete endpoint and the required auth mechanism (User API key in the api-access-token header), which the annotations do not convey. It still says nothing about pagination or result limits.

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?

The purpose is front-loaded in the first clause, and the endpoint/auth lines are compact. The trailing language/digit note is somewhat generic boilerplate, but it is short and potentially relevant to the digit-formatted IDs the tool accepts.

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?

For a simple read-only, one-parameter list call the description is close to adequate, but with no output schema the agent gets no sense of what an agent record contains or how many are returned, and pagination behavior is unaddressed.

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 the single account_id parameter is documented there as the numeric account ID. The description adds no format or sourcing detail beyond the schema, so the baseline 3 is appropriate.

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 all agents in the account" states a specific verb and resource, so the core action is unambiguous. However, the sibling set contains several other list tools (gapify_list_agent_bots, gapify_list_inbox_agents, gapify_list_team_agents), and the description offers no cue to distinguish this account-level agent list from those.

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 indication of when to choose this tool over gapify_list_agent_bots or gapify_list_team_agents, and no prerequisites are stated. The only guidance is implicit — that it is account-scoped — which the agent must infer from the resource path.

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

Deploy Server