> ## Documentation Index > Fetch the complete documentation index at: https://docs.orq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Test an MCP server tool > Executes a single tool on an upstream MCP server for testing. Connects to the server, invokes the tool with the provided arguments, and returns the result. ## OpenAPI ````yaml post /v2/mcp-servers/{id}/tools:test openapi: 3.1.0 info: title: orq.ai API version: '2.0' description: orq.ai API documentation servers: - url: https://api.orq.ai security: - ApiKey: [] tags: - name: Chunking description: Split text into smaller chunks for retrieval and generation workflows. - name: Knowledge Bases description: Create and manage knowledge bases used by agents and retrieval workflows. - name: Memory Stores description: Create and manage memory stores, memories, and memory documents. - name: Evals description: Run an evaluator against a conversation and its result - description: List models available through the AI Router. name: Models - name: Policies - name: Alerts description: >- Alerts evaluate a Reporting API metric on a fixed interval and fire notifications through notifiers when the value breaches a threshold. Each breach opens a trigger that tracks the incident until the value recovers. - name: API keys description: >- API keys authenticate programmatic access to the workspace. The unified key model exposes opaque tokens, per-domain access grants, and budget / rate-limit constraints (see ADR 0001 and ADR 0002). - name: Budgets description: >- Budgets govern spend, token usage, and request rate across six scopes: workspace, project, identity, api-key, provider, and model. A budget is hierarchical and defense-in-depth — every applicable budget is a hard gate, and the most restrictive one wins per dimension (see ADR 0007). - name: Documentation description: >- Search the orq.ai documentation. Proxies the workspace's query to the hosted docs search index. - name: Files description: File upload and retrieval operations. - name: Finder description: >- Finder entities back the studio navigation tree, project switcher, and cross-project resource references. - name: Guardrail Rules description: >- Guardrail Rules conditionally enforce evaluators and plugins for AI Gateway traffic. Rules may be scoped to a project or the whole workspace. - name: Identities description: >- Identities represent end users from your system for usage and engagement tracking. - name: Management keys description: >- Management keys are workspace-scoped credentials that authenticate programmatic access to workspace administration surfaces (API keys, budgets). Unlike project-scoped API keys, a management key always operates at the workspace level. - name: MCP Gateway description: >- Register upstream MCP servers, discover and sync their tools, and assemble gateways that expose a curated tool surface to MCP clients. - name: Model Catalog description: >- Browse the orq.ai model catalog: every model orq offers, across every provider, with pricing, capabilities and benchmark data. List endpoints only return models that are not deprecated. This API is public, requires no authentication, and is rate limited to 120 requests per minute per IP. Responses carry a 5-minute cache-control max-age. - name: Model Sharing description: >- Model sharing controls which projects a workspace model is available to. Workspace admins configure a model's Sharing (all projects / selected projects); the config ships inline on the models list response, so there is no separate read endpoint. - name: Notifiers description: Notifier destinations used to send delivery and workflow notifications. - name: Projects description: Projects organize resources within a workspace - name: Routing Rules description: >- Routing Rules conditionally select models and enforce request plugins for AI Gateway traffic. Rules are evaluated by ascending priority and may be scoped to a project or the whole workspace. - name: Skills description: >- Skills are modular instructions you can use to codify processes and conventions - name: Smart Routers description: >- Create and manage workspace Smart Routers. A Smart Router selects a model from an eligible pool for each request according to a quality, balanced, or cost profile. - name: Webhooks description: >- Create and manage webhooks that deliver workspace events to external HTTPS endpoints. - name: Workspace Security description: >- Workspace-level domain verification and IP allowlist controls. These operations are restricted to workspace administrators. - name: Workspace Settings description: >- Workspace-level settings managed with a workspace credential. A workspace is the tenant, so these settings are a singleton — there is nothing to create or delete, only read and update. - name: Responses - description: Run agents on a cron cadence. Minimum firing interval is 1 hour. name: Agent Schedules - name: Embeddings - name: Logs description: >- OpenTelemetry log query API. Search, filter, aggregate, and facet log records ingested via OTLP. - name: Reporting description: >- GenAI reporting API over canonical analytics rollups. Accepts a metric name, time range, grain, group-by, and filters; returns a typed time series and optional totals. - name: Traces description: >- Query and inspect ingested trace data: search trace summaries, aggregate metrics, and read individual traces and their spans. externalDocs: url: https://docs.orq.ai description: orq.ai Documentation paths: /v2/mcp-servers/{id}/tools:test: post: tags: - MCP Gateway summary: Test an MCP server tool description: >- Executes a single tool on an upstream MCP server for testing. Connects to the server, invokes the tool with the provided arguments, and returns the result. operationId: McpServerTestTool parameters: - name: id in: path description: Unique identifier of the MCP server. required: true schema: type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/TestMcpServerToolRequest' required: true responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/TestMcpServerToolResponse' x-code-samples: - lang: curl label: Core - Test a single tool source: | curl --request POST \ --url 'https://api.orq.ai/v2/mcp-servers/01JQ0K5R8N2ZC7X4M9T3V6HWBD/tools:test' \ --header 'Authorization: Bearer $ORQ_API_KEY' \ --header 'Content-Type: application/json' \ --data '{ "tool_name": "search_issues", "arguments": { "query": "repo:orq-ai/orquesta-web is:open label:bug" } }' - lang: python label: Python - Test a single tool source: > import os from orq_ai_sdk import Orq client = Orq(api_key=os.environ["ORQ_API_KEY"]) # tool_name is the upstream name, not a gateway's namespaced exposed_name. result = client.mcp_servers.test_tool( id="01JQ0K5R8N2ZC7X4M9T3V6HWBD", tool_name="search_issues", arguments={"query": "repo:orq-ai/orquesta-web is:open label:bug"}, ) print(result.result.ok, result.result.latency_ms) - lang: typescript label: Node.js - Test a single tool source: > import { Orq } from '@orq-ai/node'; const client = new Orq({ apiKey: process.env.ORQ_API_KEY, }); // toolName is the upstream name, not a gateway's namespaced exposedName. const { result } = await client.mcpServers.testTool({ id: '01JQ0K5R8N2ZC7X4M9T3V6HWBD', toolName: 'search_issues', arguments: { query: 'repo:orq-ai/orquesta-web is:open label:bug' }, }); console.log(result.ok, result.latencyMs); components: schemas: TestMcpServerToolRequest: required: - tool_name type: object properties: tool_name: type: string description: Bare upstream tool name, not a gateway's namespaced `exposed_name`. arguments: type: object description: Arguments passed to the tool, matching its `input_schema`. discovery_variables: type: object additionalProperties: type: string description: >- Values for the server's `template_variables`; treated as sensitive and not persisted. TestMcpServerToolResponse: type: object properties: result: $ref: '#/components/schemas/McpGatewayToolTestResult' McpGatewayToolTestResult: type: object properties: ok: type: boolean description: Whether the tool call completed successfully. result: type: object description: Payload returned by the upstream tool. latency_ms: type: integer description: Round trip time of the tool call in milliseconds. format: int32 error_message: type: string description: Human-readable reason the call failed. errors: type: array items: type: string description: Additional failure details collected during the call. securitySchemes: ApiKey: type: http scheme: bearer bearerFormat: JWT ````