Skip to main content
Glama

search_daily_notes

Read-onlyIdempotent

Busca texto en el contenido de todas las notas diarias del workspace (búsqueda ILIKE case-insensitive).

Usar cuando:
- El usuario quiere encontrar en qué día mencionó algo específico
- Buscar referencias a una persona, proyecto o tema en las notas históricas
- "¿cuándo hablé con Juan?", "¿en qué nota está el tema del contrato?"

Retorna: date y snippet con contexto (50 chars antes y 150 después de la coincidencia).
Para ver la nota completa: usar get_daily_note con la fecha encontrada.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_daily_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo resultados (default: 20)
queryYesTexto a buscar en el contenido de las notas (mínimo 2 caracteres)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description is not burdened with the safety profile; instead it adds the return shape (date plus snippet with 50 chars before and 150 after the match) and case-insensitive matching, which an agent cannot infer from annotations. It omits any note on result ordering or how the limit interacts with truncation, keeping it short of a 5.

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?

Front-loads the core action, then structures usage criteria as bullets, then the return contract, then the handoff to get_daily_note. Every sentence carries distinct information with no filler.

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 three-parameter search with no output schema, the description supplies the missing return contract, the matching semantics, and the natural follow-up tool, which is everything an agent needs to invoke it and act on the result.

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 including the omit-for-all-workspaces behavior are already documented in the schema. The description's phrase 'del workspace' is slightly narrower than the workspace_id default of all workspaces in one call, but it adds no new parameter-level detail beyond 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?

States a specific verb and resource ('Busca texto en el contenido de todas las notas diarias del workspace') plus the matching semantics (ILIKE case-insensitive). It also distinguishes itself from the sibling that retrieves full notes by pointing to get_daily_note for the complete record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

An explicit 'Usar cuando' block lists three concrete scenarios and two natural-language example queries ('¿cuándo hablé con Juan?'), and the description names the follow-up tool with its condition. There is no ambiguity about when this tool is the right choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources