Jiji MCP

jiji_capabilities

Read-onlyIdempotent

Inspect mapped feature catalogs, readable resources, approved action schemas, and owner handoffs to understand supported marketplace tasks before searches, seller comparisons, or message handoffs.

Instructions

Inspect the full mapped feature catalog, supported read resources, owner-approved action schemas, and owner handoffs. A mapped feature is not a claim that every write was live-tested.

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": "jiji_capabilities"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`section`	No		overview

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Oct 29, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable caveat that 'a mapped feature is not a claim that every write was live-tested,' which discloses a reliability limitation beyond the annotations.

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 core purpose and followed by a useful caveat. There is no redundant wording or filler.

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

Completeness3/5

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

The description is adequate for understanding the tool's purpose, and an output schema exists so return values need not be explained. However, with two parameters and 0% schema description coverage, it omits how to invoke the tool using 'name' and 'section', leaving an invocation gap.

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

Parameters2/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 carry parameter meaning, but it never mentions the 'name' or 'section' parameters. The listed content areas loosely correspond to section enum values, yet the description does not explain filtering, defaults, or what 'name' does.

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

Purpose4/5

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

The description clearly states that the tool inspects a mapped feature catalog, supported reads, action schemas, and owner handoffs, giving a specific verb and resource set. It does not explicitly differentiate itself from sibling tools such as jiji_inspect_workflow or jiji_action_status, but the catalog-inspection purpose is distinct enough to identify.

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

Usage Guidelines3/5

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

Usage is implied by 'Inspect' and the list of content areas, but there is no explicit guidance on when to choose this tool over siblings or when not to use it. An agent can infer it is a discovery tool, but the description does not say 'use this before calling other tools' or name alternatives.

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