JEV

JEV Route API MCP

Find a relevant data API or content evaluation tool for a task. Call the JEV Route (API Finder) API via REST or MCP with your Nexscope API key.

Cost10 credits / callOnline Test

JEV Route API AI Prompts & Use Cases

After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.

New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.

1. Find A Tool For A Research Task

Prompt: Find a published tool for [research intent]. Show the returned match or candidates and ask for clarification if the intent is ambiguous. Do not execute the suggested tool.

2. Find A Tool Within A Category

Prompt: Find a published tool for [research intent] within [current catalog category]. Keep discovery separate from any later tool execution.

3. Find A Suitable Evaluation Preset

Prompt: Find a fixed evaluation preset for [evaluation intent]. Show the relevant preset information without converting my intent into an evaluation request.

What You Need to Provide

Step 1 · Connect

Connect Your AI Assistant

Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json

Authentication

Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx

Using an API key? Get your key from API Access and include it in the Authorization header shown above.

Call this MCP tool

MCP tool name

nexscope_route_api

MCP endpoint

https://api.nexscope.ai/mcp

JSON-RPC method

tools/call

Initialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.

{
  "jsonrpc": "2.0",
  "id": "jev-route-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_route_api",
    "arguments": {
      "categorySlug": "amazon-marketplace-intelligence",
      "intent": "Fetch Amazon product reviews by ASIN so I can analyze customer pain points"
    }
  }
}

MCP 2025-11-25 · Streamable HTTP

Progress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.

Arguments

Name	Type	Required	Description
`intent`	`string`	required	One routing intent. It is used only for discovery and is never converted into API or evaluation input. Example: Fetch Amazon product reviews by ASIN so I can analyze customer pain points
`categorySlug`	`string`	optional	Optional current public catalog category, or jev-evaluation to limit discovery to the fixed presets. Example: amazon-marketplace-intelligence

Response fields

Treat structuredContent as the programmatic API response payload.

Name	Type	Required	Description
`code`	`integer`	required	Zero on success; non-zero for validation, access, quota, or availability errors.
`data`	`object`	required	For matched, call the returned endpoint separately after collecting its required fields. For ambiguous, ask the user to clarify and route again. For no_match, do not invent or execute a capability.
`data.candidates`	`array`	required	Up to three clarification candidates for an ambiguous result.
`data.candidates[]`	`object`	required	Up to three clarification candidates for an ambiguous result.
`data.catalogVersion`	`string`	required	Catalog timestamp used for this routing decision.
`data.confidence`	`number \| null`	required	Confidence value used by this API operation. Minimum: 0 Maximum: 1
`data.match`	`any`	required	Null for ambiguous and no_match responses.
`data.models`	`array`	required	Resolved model versions used by the routing stages.
`data.models[]`	`string`	required	Resolved model versions used by the routing stages.
`data.policyVersion`	`string`	required	Server-owned routing policy version.
`data.reason`	`string`	required	Reason value used by this API operation. Allowed: matched, clarification_required, no_supported_api
`data.status`	`string`	required	Status value used by this API operation. Allowed: matched, ambiguous, no_match
`msg`	`string`	required	Response message.

Published data API match

Name	Type	Required	Description
`data.match`	`object`	required	Null for ambiguous and no_match responses.
`data.match.docsPath`	`string`	required	Docs path value used by this API operation.
`data.match.endpoint`	`string`	required	Endpoint value used by this API operation.
`data.match.kind`	`string`	required	Kind value used by this API operation. Constant: skill_api
`data.match.mcpToolName`	`string`	required	Mcp tool name value used by this API operation.
`data.match.method`	`string`	required	Method value used by this API operation. Constant: POST
`data.match.name`	`string`	required	Name value used by this API operation.
`data.match.schemaEndpoint`	`string`	required	Schema endpoint value used by this API operation.
`data.match.slug`	`string`	required	Slug value used by this API operation.

Fixed JEV use-case match

Name	Type	Required	Description
`data.match`	`object`	required	Null for ambiguous and no_match responses.
`data.match.docsPath`	`string`	required	Docs path value used by this API operation.
`data.match.endpoint`	`string`	required	Endpoint value used by this API operation.
`data.match.kind`	`string`	required	Kind value used by this API operation. Constant: jev_use_case
`data.match.mcpToolName`	`string`	required	Mcp tool name value used by this API operation.
`data.match.method`	`string`	required	Method value used by this API operation. Constant: POST
`data.match.name`	`string`	required	Name value used by this API operation.
`data.match.schemaEndpoint`	`string`	required	Schema endpoint value used by this API operation.
`data.match.schemaPointer`	`string`	required	Schema pointer value used by this API operation.
`data.match.useCase`	`string`	required	Use case value used by this API operation.

One of option 3

Name	Type	Required	Description
`data.match`	`null`	required	Null for ambiguous and no_match responses.

Format Illustration

Illustrative example with fictional data, not a live tool call.

Illustrative Question

Find a tool to retrieve Amazon product reviews by ASIN for customer-pain-point research.

Illustrative Response Explanation

The illustrative route points to Amazon Reviews List. This is discovery metadata only: no ASIN has been queried and no review analysis has run.

About this sample: Illustrative format example with fictional values, not a live tool call. Replace example inputs with your own permitted assets or public identifiers. Model and catalog labels in this illustration are fictional, not identifiers to select for a live request.

Published sample data is not available for this page. A format illustration or workflow guide is not a substitute for a published result.

View the MCP Request & Response Format

Examples