Skip to main content
Glama
liliangshan

MCP Project Standards Server

by liliangshan

api_config

Get, set, update base URLs and headers, add endpoints, and search or list configured APIs to manage API configurations.

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, and the description does not disclose behavioral traits such as side effects of mutations (e.g., 'set', 'updateHeaders', 'deleteHeader'), required permissions, or whether changes are reversible. It relies on the action names to imply behavior.

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 followed by examples, which is concise and efficient. However, the examples could be better integrated into a structured format like bullet points, but the current form is acceptable.

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?

The description does not explain what is returned by actions like 'get' or 'list', nor does it describe the overall config structure. Given the tool's complexity (7 parameters, nested objects), this is a notable gap.

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%, so the description adds little beyond what the schema already provides. The examples mirror the action enum but do not add new semantic meaning.

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' and lists specific example actions like 'get config', 'set baseUrl', 'updateHeaders', 'search APIs', 'list all configured APIs', which distinguish it from sibling tools like api_execute or 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 provides examples but does not explicitly state when to use this tool versus siblings like api_execute. It implies configuration management usage, but lacks clear exclusions or alternatives.

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-project-standards'

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