Skip to main content
Glama

jp_lit_search_guides_cases

Search reference cases to find similar questions, answer processes, and reference materials for advancing your research.

Instructions

レファレンス協同データベースのレファレンス事例を検索する。類似質問、回答プロセス、参考資料を調査の次の一手の材料として参照するためのツール

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo
pageNo
lib_idNo
lib_groupNo
force_refreshNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
typeYes
pageYes
limitYes
totalYes
itemsYes
rawYes
cacheNo

Implementation Reference

  • Main handler function that parses input, calls crdClient.searchCases() with caching, validates output via guidesCasesOutputSchema, and returns structured content.
    export function createJpLitSearchGuidesCasesTool(
      crdClient: CrdClient,
      cache: FileCache = createFileCache(),
      sessions: SessionStore = createSessionStore()
    ) {
      return async (input: unknown) => {
        const parsed = guidesCasesInputSchema.parse(input);
        const { force_refresh, ...cacheableInput } = parsed;
    
        const result = await runCachedTool<GuidesCasesOutput>({
          tool: "jp_lit_search_guides_cases",
          input: cacheableInput as Record<string, unknown>,
          cache,
          sessions,
          bypassCache: force_refresh,
          live: async () =>
            guidesCasesOutputSchema.parse(
              await crdClient.searchCases({
                query: parsed.query,
                limit: parsed.limit,
                page: parsed.page,
                lib_id: parsed.lib_id,
                lib_group: parsed.lib_group
              })
            )
        });
        const structuredContent = guidesCasesOutputSchema.parse(
          withToolCache(result.structuredContent as Record<string, unknown>, result)
        );
    
        return {
          content: [{ type: "text" as const, text: JSON.stringify(structuredContent, null, 2) }],
          structuredContent
        };
      };
    }
Behavior2/5

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

No annotations provided; description does not disclose whether the tool is read-only, has side effects, authentication needs, or rate limits. Only states 'search' and 'refer', leaving behavioral traits unspecified.

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?

Single sentence effectively covers purpose and usage context with no redundant content, front-loading the key action and resource.

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?

Given the presence of output schema and 6 parameters, the description lacks details on return format, pagination, parameter roles, and how this tool differs from similar search tools. Incomplete for effective use.

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 has 0% parameter description coverage; the description adds no explanation for any of the 6 parameters (query, limit, page, lib_id, lib_group, force_refresh), relying solely on the schema's basic type/default info.

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?

Description states the tool searches reference cases in a specific database and explains its purpose for finding similar questions and materials. However, it does not distinguish from sibling tools like 'jp_lit_search' or 'jp_lit_search_guides_manuals'.

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?

Implies usage for researching reference cases as next-step materials, but lacks explicit when-to-use or when-not-to-use guidance or comparison with alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/itarunnn/jp-lit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server