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

gapify-mcp-server

by mh-zeynal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

AgentBots: List all AgentBots

gapify_platform_list_agent_bots
Read-onlyIdempotent

List all agent bots available in Gapify so you can review support automation resources and use their IDs for API-driven workflows.

Instructions

List all agent bots available [AgentBots] GET /platform/api/v1/agent_bots Auth: Platform app 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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/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 still adds real context beyond that: the required auth mechanism (Platform app API key in the `api-access-token` header) and the encoding caveat about Persian/Arabic-Indic digits, which an agent would not learn from the annotations or the empty schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded and the endpoint and auth lines are terse and useful. The trailing sentence about Persian/Arabic-Indic digits is boilerplate that does not earn its place on a zero-parameter read tool and slightly muddies the description.

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 parameterless read-only list tool whose annotations already carry the safety profile, the description covers purpose, endpoint, and auth, which is enough to invoke it correctly. With no output schema present, a brief note on the shape of the returned list would have closed the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The only parameter-adjacent note (language/digit handling) concerns values sent, of which there are none here.

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 states a specific verb and resource ('List all agent bots available') and pins the exact endpoint (GET /platform/api/v1/agent_bots), so the agent knows precisely what it returns. It does not, however, distinguish this platform-API variant from the near-identical sibling `gapify_list_agent_bots`, leaving the agent to guess which of the two to pick.

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 and no mention of alternatives. With siblings `gapify_list_agent_bots`, `gapify_get_agent_bot`, and the create/update/delete agent-bot tools all present, the agent gets no help deciding between the list, the single-get, or the non-platform duplicate.

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