Skip to main content
Glama
Sign In
Xzar MCP Server

Xzar MCP Server

Official
by xzar-si
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search the case's reference library

search_library
Read-onlyIdempotent

Search a case's prior-art reference library to find evidence before deciding; returns matching publication IDs, titles, and snippets for review.

Instructions

Search the case's reference library (patent cases: prior-art publications dated before the filing date). Use it to find evidence before deciding. Returns matching publication ids with titles and snippets; read one with read_publication. Counts against the tool budget.

Input Schema

NameRequiredDescriptionDefault
queryYesKeywords or a short phrase describing the technology, e.g. 'battery cell cooling plate'
episode_idYesThe episode id returned by start_task, e.g. ep_3f9c2a1b0d4e5f6a7b8c9d0e

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.3
    • addedInput schema / properties / episode_id / description
      Added value: +"The episode id returned by start_task, e.g. ep_3f9c2a1b0d4e5f6a7b8c9d0e"
    • addedInput schema / properties / query / description
      Added value: +"Keywords or a short phrase describing the technology, e.g. 'battery cell cooling plate'"
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds the non-obvious cost signal ('Counts against the tool budget') and describes the shape of results (publication ids, titles, snippets) even though there is no output schema.

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

Conciseness4/5

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

Compact and front-loaded: domain definition, usage intent, return shape and next step, and cost warning. 'Use it to find evidence before deciding' is slightly generic but still orients the agent.

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?

No output schema exists, yet the description explains return values and next steps, and covers the budget cost. It does not mention result limits or pagination, which would complete the picture for repeated searching.

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%, so both parameters are already well documented in the schema. The description adds no extra syntax, constraints, or interpretation beyond what the schema provides, which is the baseline when the schema does the work.

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?

States a specific verb and resource and immediately clarifies what the reference library contains for patent cases (prior-art publications dated before the filing date). It also distinguishes itself from the read_publication sibling by name.

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?

Explicitly frames the tool as an evidence-gathering step before deciding, and routes the agent to read_publication for reading a hit. It does not clarify its boundary versus search_rules, which is the main adjacent alternative.

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