Ninja MCP

Overview Schema Source Related Servers Discussions Admin

Discover Vertical Context

ninja_discover_vertical_context

Resolve vertical availability for a saved address or coordinates. Checks if retail, pharmacy, beauty, or restaurant verticals are accessible for ordering.

Instructions

Resolve vertical availability for a saved address or coordinates. Product verticals include store/search context; restaurants use separate branch/menu tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ninja_discover_vertical_context"
  }
}

Input Schema

Name	Required	Default
`latitude`	No
`vertical`	No	RETAIL
`addressId`	No
`longitude`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 15, 2026

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It only says 'resolve vertical availability' without explaining what that entails (e.g., returns boolean, requires auth, side effects). Lacks behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the main action, no unnecessary words. Each sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 4 params (none required), no output schema, and no annotations, the description is insufficient. It does not explain what 'vertical availability' means, response format, or how parameters interact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it does not explain any parameter. It only hints that addressId or lat/long are used. No parameter meaning or usage guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool resolves vertical availability for a saved address or coordinates, and distinguishes it from restaurant tools by mentioning separate branch/menu tools. The verb 'resolve' and resource 'vertical availability' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says restaurants should use separate tools, providing a when-not-to-use guideline. However, it does not explicitly state when to use this tool over alternatives like ninja_discover_retail_context, but implies it for product verticals.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.