Skip to main content
Glama
OrgMentem

zotio

by OrgMentem
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Go
Hybrid

search

Read-only

Find items in synced data via full-text search, with an option to search PDF text and resolve hits to parent items.

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

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 25, maximum 100)
queryYesSearch query (supports FTS5 syntax: AND, OR, NOT, quotes for phrases)
fulltextNoSearch only synced PDF text and return parent item context

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. First observedv0.7.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint true and destructiveHint false, so the safety profile is covered. The description adds operational constraints: the requirement to sync first and the bounding of large responses to the MCP tool-result budget. These are behavioral disclosures beyond annotations and help the agent anticipate side conditions. No contradiction with 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?

The description is four short sentences, each earning its place: purpose, fulltext usage, prerequisite, and response budget. It is front-loaded with the core purpose and immediately gives actionable guidance. There is no filler or redundancy.

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?

For a tool with 3 parameters and no output schema, the description covers the main operational aspects: what it searches, the sync prerequisite, the response budget, and a hint for the fulltext flag. However, it does not describe the return format or how results are structured when fulltext is false, nor does it elaborate on what 'synced data' includes. Given there is no output schema, a bit more detail on expected results would improve completeness, but it is adequate for the schema-covered parameters.

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 each parameter is already documented. The description adds a functional hint for fulltext by explaining how it resolves PDF-text hits to parent items, but this largely rephrases the schema's parameter description. The added value is marginal; the baseline of 3 applies because the schema does the heavy lifting.

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 states a specific verb and resource: 'Full-text search across synced data.' It clearly identifies what the tool does. While there is a sibling command_search, the description does not explicitly differentiate the two, but the 'synced data' qualifier implies a distinct scope. It is clear enough to guide selection, though it could more explicitly contrast with command_search.

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?

The description gives a prerequisite ('Requires sync first') and a specific use for the fulltext parameter ('Set fulltext to resolve synced PDF-text hits to parent items'). However, it does not explain when to prefer this tool over command_search or other siblings, nor does it indicate when not to use it. The context is provided but no explicit exclusions or alternative routing.

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