Skip to main content
Glama
OrgMentem

zotio

by OrgMentem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

search

Read-only

Full-text search across synced data. Set fulltext to resolve synced PDF-text hits to parent items. Requires sync first. Large responses are bounded to the MCP tool-result budget.

Instructions

Full-text search across synced data. Set fulltext to resolve synced PDF-text hits to parent items. Requires sync first. Large responses are bounded to the MCP tool-result budget.

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 25, maximum 100)
queryYesSearch query (supports FTS5 syntax: AND, OR, NOT, quotes for phrases)
scopeNoItem cohort: library | collection:KEY | tag:NAME | item:KEY | query:TEXT | saved-search:KEY; join arms with AND to intersect them, e.g. collection:KEY AND tag:NAME; requires fulltext. Membership applies before ranking and limit.
fulltextNoSearch only synced PDF text and return parent item context

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.29.0
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "Item cohort: library | collection:KEY | tag:NAME | item:KEY | query:TEXT | saved-search:KEY; join arms with AND to intersect them, e.g. collection:KEY AND tag:NAME; requires fulltext. Membership applies before ranking and limit.",
+  "type": "string"
+}
  2. Changed4 schema fields changedv0.21.0
    • addedInput schema / properties / fulltext
      Added value: +{
+  "description": "Search only synced PDF text and return parent item context",
+  "type": "boolean"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 25)"New value: +"Max results (default 25, maximum 100)"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
  3. First observedv0.7.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnly, non-destructive, and open-world behavior, so the description need only add context — and it does, disclosing the sync prerequisite and that large responses are truncated to the tool-result budget. It stops short of describing result shape or pagination, but the truncation warning is genuinely useful pre-call information.

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?

Four short sentences, front-loaded with the core purpose, and each remaining sentence earns its place by adding a prerequisite, a parameter hint, or an output-size caveat. No filler.

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?

With annotations covering the safety profile and a fully documented schema, the description supplies the two things structured fields cannot: the sync prerequisite and response bounding. It leaves the searched data scope ('synced data') somewhat vague, which is the only real gap.

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 description coverage is 100%, so the schema carries the parameter burden (FTS5 syntax, scope arms, limit bounds). The description only elaborates on the fulltext parameter's parent-item resolution, adding marginal meaning beyond the schema's own wording. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Full-text search across synced data', plus the fulltext-mode behavior of resolving PDF-text hits to parent items. It is clear on its own, but never differentiates itself from the sibling tools command_search or sql, which an agent must disambiguate against.

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?

Gives a concrete prerequisite ('Requires sync first') and a conditional instruction for when to use the fulltext flag. It does not name any alternative tool or state when NOT to use this search, so the routing guidance is context-rich but not exhaustive.

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