invokit-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INVOKIT_API_KEY | Yes | Your invok.it API key |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_toolsA | Search the invok.it marketplace for AI agent tools using natural language. Args: query: Natural language search query (e.g. "send email", "image recognition"). category: Filter by category slug (use list_categories to see available ones). min_quality_score: Minimum quality score (0-100). max_price_per_call: Maximum price per API call in USD. page: Page number for pagination. per_page: Results per page (max 100). |
| get_toolB | Get full details for a specific tool by its slug. Args: slug: The tool's unique identifier (e.g. "send-email-via-sendgrid"). |
| list_categoriesA | List all tool categories with counts of tools, skills, and apps. |
| search_skillsA | Search for skills (multi-tool workflows) on invok.it. Args: query: Natural language search query (e.g. "pdf to summary", "data pipeline", "content moderation"). category: Filter by category slug. pricing_type: Filter by "free" or "paid". tags: Comma-separated tags to filter by. page: Page number. per_page: Results per page. |
| get_skillB | Get full details for a specific skill by its slug. Args: slug: The skill's unique identifier. |
| search_appsB | Search for apps (deterministic step pipelines) on invok.it. Args: query: Natural language search query (e.g. "document processing", "image analysis pipeline", "ETL workflow"). category: Filter by category slug. pricing_type: Filter by "free" or "paid". tags: Comma-separated tags to filter by. page: Page number. per_page: Results per page. |
| get_appA | Get full details for a specific app by its slug. Args: slug: The app's unique identifier. |
| invoke_toolA | Invoke a tool on the invok.it marketplace via transparent proxy. Requires an API key (INVOKIT_API_KEY environment variable). Check the tool's input_schema first (via get_tool) to know what arguments to pass. The response includes the tool's output along with platform metadata (latency, tool version, invocation ID if available). After receiving the result, use submit_outcome to provide quality feedback on the tool. This helps improve tool rankings for all agents. On failure, error responses include an error code (e.g. CIRCUIT_OPEN, RATE_LIMIT_EXCEEDED, TOOL_NOT_FOUND), a suggestion for resolution, and alternative tools when available (on 503). Use this information to automatically recover — switch to an alternative tool or retry after the suggested delay. Args: slug: The tool's slug identifier (e.g. "send-email-via-sendgrid"). arguments: JSON arguments matching the tool's input_schema (use get_tool to see the schema). version: Specific tool version to invoke (e.g. "1.0.0"). Uses latest if omitted. |
| get_tool_qualityA | Get the quality score breakdown for a tool — an overall 0-100 score with primary signals (success rate, schema honesty, latency consistency) and secondary signals. Use this to evaluate whether a tool is reliable enough to use. For detailed latency percentiles and raw performance data, use get_tool_metrics instead. Args: slug: The tool's slug identifier. period: Time period — "hour", "day", "week", "month", or "all_time". |
| get_tool_metricsA | Get raw performance metrics for a tool — invocation counts, latency percentiles (p50/p95/p99), error rate, and uptime. Use this for detailed performance analysis. For a simple reliability check with an overall score, use get_tool_quality instead. Args: slug: The tool's slug identifier. period: Time period — "hour", "day", "week", "month", or "all_time". |
| get_tool_alternativesA | Find type-compatible alternative tools from the same category. Useful when a tool's circuit breaker is open or you want to compare options. Args: slug: The tool's slug identifier. limit: Maximum number of alternatives to return (default 5). |
| get_manifestA | Get the invok.it platform manifest — capabilities, endpoints, auth methods, and rate limits. |
| check_usageA | Check your current API usage, quota, and remaining calls for this month. Requires an API key (INVOKIT_API_KEY environment variable). Use this before invoking tools to ensure you have remaining quota. |
| submit_outcomeA | Submit quality feedback after invoking a tool. This closes the feedback loop: search → invoke → report outcome. Outcomes improve quality scores and help other agents choose better tools. Requires an API key (INVOKIT_API_KEY environment variable). Args: slug: The tool's slug identifier that was invoked. invocation_id: The invocation ID from invoke_tool's response metadata. agent_id: A stable identifier for your agent (default: "mcp-client"). Use a custom value like "my-chatbot-v2" to track feedback by agent. semantic_accuracy: How accurately did the output match the expected result? 0.0 = completely wrong, 0.5 = partially correct, 1.0 = perfect. output_usefulness: How useful was the output for your task? 0.0 = useless, 0.5 = somewhat helpful, 1.0 = exactly what was needed. task_completion: Did the tool complete the intended task? feedback_text: Optional free-text feedback (max 2000 chars). |
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 14 tools
Every tool targets a distinct action and resource: quality scores, raw metrics, alternatives, tool details, skills, apps, categories, invocation, and feedback are all clearly separated. The two most similar tools, get_tool_quality and get_tool_metrics, explicitly cross-reference each other to eliminate ambiguity.
Tool names consistently follow a verb_noun snake_case pattern across get, search, list, check, submit, and invoke. Entity types like tool, skill, app, and category appear in predictable positions, making the naming scheme easy to learn and anticipate.
14 tools is well within the ideal range for a marketplace platform server. Each tool covers a necessary step in the workflow: discover, inspect, check usage, invoke, give feedback, and retrieve platform metadata. No tool feels redundant or extraneous.
The tool surface covers the full marketplace lifecycle: searching and retrieving tools/skills/apps/categories, inspecting quality and raw metrics, finding alternatives, checking quota, invoking tools, and submitting outcome feedback. The only possible gap would be direct invocation of skills or apps, but those are not advertised as invocable resources.