MCP Omni-Tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTCLEAR_API_KEY | Yes | Your AgentClear API key starting with axk_ |
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 |
|---|---|
| discoverA | Find APIs by describing what you need in natural language. Returns ranked services with pricing and trust scores from the AgentClear marketplace. |
| callA | Call a discovered API service through AgentClear's metered proxy. Billed per call. Pass the service_id from a discover result and your payload. |
| discover_and_callA | One-shot: find the best matching API for your query and call it immediately. Combines discover + call in a single step. |
| list_servicesC | Browse all available services on the AgentClear marketplace with optional filtering. |
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 4 tools
Each tool has a clearly distinct purpose: call invokes a discovered service, discover finds APIs, discover_and_call combines both, and list_services browses the marketplace. No overlap in functionality.
Tool names follow a consistent verb-based pattern (call, discover, list_services). The compound discover_and_call is a minor deviation but still clear and predictable.
With 4 tools, the set is well-scoped for an API discovery and calling service. It covers the essential interactions without unnecessary bloat, though a few more tools (e.g., authentication) could be added without clutter.
The tool surface covers the core workflow: discover APIs, browse services, and call them. The combined discover_and_call streamlines common usage. Minor gaps like account management or call history are reasonable omissions for a focused tool.