Skip to main content
Glama
Sign In
NINJAMCP

NINJAMCP

by omikirin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

search_lore

Search across character settings and world lore by keyword. Find characters or setting details from ninja techniques, weapons, relationships, and more.

Instructions

キーワードでキャラ設定・世界観テキストを横断全文検索する。忍術名・武器・関係性・設定の断片から該当キャラや設定箇所を探すときに使う。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_lore"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes検索キーワード。例: '双子' '刀' '天狗'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It describes the tool as a full-text search, which implies read-only behavior, but does not explicitly state side effects, auth requirements, or rate limits. Adequate but lacks detail.

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 conveying purpose, scope, and usage context without any fluff. Efficient and front-loaded.

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

Completeness4/5

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

Single parameter, no output schema. Description explains what is searched and when to use. Missing details like result format, but sufficient for a simple search tool.

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

Parameters3/5

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

Schema coverage is 100% with a brief description. The tool description adds example keywords ('双子', '刀', '天狗') which provide concrete guidance beyond the schema. Baseline 3 is appropriate as schema already covers the parameter meaning.

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?

Description clearly states the verb 'search' and the resource 'lore texts' (character settings and world-building). It specifies the use case of finding related characters or settings from fragments, and distinguishes from sibling tool 'get_character_image'.

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?

Description indicates when to use: searching for characters or settings from keywords like ninjutsu names, weapons, relationships. It does not explicitly state when not to use or mention alternatives, but the sibling tool context implies the distinction.

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

Deploy Server

Other Tools