tanilo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| researchA | Perform real-time research on any topic using AgentOracle. Returns structured results with summary, key facts, cited sources, and confidence score. Costs $0.02 USDC per query via x402 on Base mainnet. |
| deep-researchA | Perform comprehensive deep research on any topic using AgentOracle Sonar Pro. Returns expert-level analysis with 10-15 detailed facts, in-depth analysis paragraph, cited sources, and confidence score. Costs $0.10 USDC per query via x402 on Base mainnet. Use for complex topics requiring thorough analysis. |
| check-healthA | Check if the AgentOracle API is online and get service status including uptime, model info, and pricing. |
| get-manifestA | Get the AgentOracle x402 payment manifest. Returns payment requirements, supported networks, pricing, and endpoint details for programmatic integration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| api-docs | AgentOracle API documentation — endpoints, pricing, and integration guide |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: check-health verifies API status, deep-research provides comprehensive analysis, get-manifest retrieves payment details, and research offers basic real-time research. There is no overlap in functionality, and the descriptions clearly differentiate their scopes and use cases.
All tool names follow a consistent kebab-case pattern with clear verb-noun combinations: check-health, deep-research, get-manifest, and research. The naming is predictable and readable, with no deviations in style or convention.
With 4 tools, the set is well-scoped for the AgentOracle MCP server's purpose, covering API health checks, payment integration, and two tiers of research functionality. Each tool earns its place without redundancy, making the count appropriate for the domain.
The tool surface covers core functionalities: API status, payment details, and research operations with basic and deep tiers. A minor gap exists in lacking explicit CRUD operations for managing research queries or payment settings, but agents can work around this given the server's focus on querying and integration.