Skip to main content
Glama
Sign In
gapify-mcp-server

gapify-mcp-server

by mh-zeynal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Account AgentBots: List all AgentBots

gapify_list_agent_bots
Read-onlyIdempotent

List every agent bot available for a specific account to view support automation options. Provide the numeric account ID and authenticate with your API key.

Instructions

List all agent bots available for the current account [Account AgentBots] GET /api/v1/accounts/{account_id}/agent_bots 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_agent_bots"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesThe numeric ID of the account

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already supply the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description adds genuinely useful behavioral context beyond them: the auth mechanism (User API key in the `api-access-token` header). It stops short of describing return shape or pagination.

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?

Well front-loaded: the list action, endpoint, and auth are stated in compact order. The trailing Persian/Arabic-Indic digit note is generic boilerplate that earns little place on a read-only list tool with a single ID parameter.

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 list tool with annotations covering its safety profile this is mostly adequate, but there is no output schema and the description never says what is returned (fields, pagination). The duplicated sibling also goes 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 sole account_id parameter is already documented in the schema. The description adds no syntax or format detail beyond 'current account', so the schema carries the load and baseline 3 applies.

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+resource+scope ('List all agent bots available for the current account') and even gives the endpoint. It is clear in isolation, but it does not distinguish itself from the near-identical sibling gapify_platform_list_agent_bots, which leaves the agent unable to choose between them from the description alone.

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 when-to-use guidance, no prerequisites, and no alternative named, despite a near-duplicate sibling (gapify_platform_list_agent_bots) and related getters. The agent must infer the usage context entirely.

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