agent-api-gateway-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_BASE_URL | No | Base URL for the API | https://agentapigw.dpdns.org/v1 |
| AGENT_API_KEY | Yes | API key from dashboard |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract | Extract structured data from a public URL. schema: product | article | company. Returns validated JSON fields. |
| extract_productC | Extract product fields (name, price, stock, rating, variants) from a URL. |
| extract_articleA | Extract article fields (title, author, date, topics, summary) from a URL. |
| extract_companyB | Extract company fields (name, description, location, industry) from a URL. |
| list_schemasA | List available extraction schemas and field definitions. |
| get_usageA | Return current plan tier, credits used, and credits remaining for this API key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each extraction tool targets a distinct entity (product, article, company), and the administrative tools (list_schemas, get_usage) serve different purposes. No overlap or ambiguity exists.
Extraction tools follow a consistent 'extract_<entity>' pattern. The administrative tools use different verb prefixes ('list_', 'get_') which is acceptable given their distinct roles, though slightly deviates from the main pattern.
With 5 tools covering extraction, schema listing, and usage tracking, the count is well-scoped for an API gateway. No tools feel redundant or missing.
The set covers common extraction needs and provides schema and usage information. However, it lacks tools for managing schemas (create/update/delete) or extracting additional entity types, which would make it more complete.