Skip to main content
Glama
liliangshan

mcp-server-apidebug

by liliangshan

default_api_config

Manage API configurations with actions to get, set, update base URL, update or delete headers, add API endpoints, search, and list all configured APIs.

Instructions

API configuration management tool for managing API settings, endpoints, and configurations. Examples: get config, set baseUrl to "https://api.example.com", updateHeaders with {"Authorization":"Bearer token"}, search APIs by keyword, list all configured APIs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: "get" to retrieve config, "set" to update config, "updateBaseUrl" to update base URL, "updateHeaders" to update headers, "deleteHeader" to delete header, "addApi" to add API endpoint, "search" to search APIs, "list" to list all APIs
configNoAPI configuration (required for "set" action)
baseUrlNoNew base URL (required for "updateBaseUrl" action)
headersNoNew headers to add or update (required for "updateHeaders" action)
headerNameNoName of header to delete (required for "deleteHeader" action)
apiNoAPI configuration (required for "addApi" action)
keywordNoSearch keyword (required for "search" action)
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions actions like 'set' and 'updateHeaders' but does not explain side effects (e.g., whether updates merge or overwrite), persistence, permissions, or error handling. This is insufficient for a mutation tool.

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 description is a single sentence plus a list of examples, which is concise and front-loaded with purpose. However, the examples could be integrated more seamlessly, and there is minor redundancy (e.g., 'get config' repeats the action enum).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (7 parameters, nested objects, 8 actions) and no output schema, the description lacks completeness. It does not explain return values, behavior per action, or error handling. The schema covers parameters but the description fails to provide overarching guidance.

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?

The input schema has 100% coverage with detailed descriptions for each parameter. The description adds examples but does not provide new semantic meaning beyond what is already in the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is an 'API configuration management tool for managing API settings, endpoints, and configurations.' The examples list specific actions (get, set, updateBaseUrl, updateHeaders, search, list) which distinguish it from sibling tools like default_api_execute or default_api_debug.

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

Usage Guidelines3/5

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

The description implies usage through examples but does not explicitly state when to use this tool versus alternatives. No guidance on prerequisites, such as needing a configured API before using default_api_execute, is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/liliangshan/mcp-server-apidebug'

If you have feedback or need assistance with the MCP directory API, please join our Discord server