Skip to main content
Glama
Sign In

livediagram

by app.livediagram.mcp
OverviewDiscussionsAdmin

Find documents

find_documents
Read-only

Search the user’s documents by name — their personal library AND the shared libraries of every team they belong to. Returns a compact list (id, name, updated time, which library it lives in, and a link to open it). Lightweight and image-free so you can scan many results, then read_document the one you want.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20).
queryNoOnly documents whose name, or whose folder's name, contains each word of this text (any case).
archivedNotrue: only the user's archived documents (archived ones are never listed otherwise). Each can be moved back with unarchive_document.

Output Schema

NameRequiredDescriptionDefault
countYesHow many documents matched.
documentsYesThe matches, most recently saved first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / archived
      Added value: +{
+  "description": "true: only the user's archived documents (archived ones are never listed otherwise). Each can be moved back with unarchive_document.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / documents / items / properties / archived
      Added value: +{
+  "const": true,
+  "description": "Present when the document is archived: unarchive_document moves it out.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedOutput schema / properties / documents / description
      Previous value: -"The matches, most relevant first."New value: +"The matches, most recently saved first."
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Only documents whose name contains this text."New value: +"Only documents whose name, or whose folder's name, contains each word of this text (any case)."
  4. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds value by disclosing the payload shape (id, name, updated time, owning library, link) and that results are image-free/lightweight for high-volume scanning. It doesn't address result caps or ordering, but the behavioral picture is well beyond the 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?

Two sentences, zero filler, with the scope (personal + team libraries) front-loaded before the return-shape and next-step guidance. Every clause carries information.

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

Completeness5/5

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

For a read-only, zero-required-parameter search with full schema coverage and an output schema, the description covers scope, result contents, and the follow-up call. Nothing an agent needs to select and invoke it correctly is missing.

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 all three parameters are already documented, including the non-obvious archived behavior. The description adds only the high-level 'by name' framing and says nothing extra about limit or the archived toggle, so it neither compensates for nor extends the schema.

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?

Specific verb (search by name) plus resource (documents) plus explicit scope: the personal library AND every team's shared library. It also distinguishes itself from read_document, so an agent knows this is the scanning tool, not the reading tool.

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?

It states the workflow clearly — scan many compact results here, then call read_document on the one you want — which is real when-to-use guidance tied to a named sibling. It stops short of explicit exclusions (e.g., when to skip this and go straight to read_document by id), so not a 5.

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

All livediagram toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources