Skip to main content
Glama

cronos_cerca

Search diary files (raw, todo, chiusura) for any text using case-insensitive regex. Find when you worked on a project, ticket, or made a decision.

Instructions

Cerca testo nei file del diario (raw, todo, chiusura).

Ricerca full-text case-insensitive con supporto regex. Per default cerca su tutte e tre le sorgenti (raw, todo, chiusura). Utile per trovare quando si e' lavorato su un progetto, ticket, argomento, o quando una decisione e' stata presa, o cosa c'era da fare.

Usa questo tool quando l'utente chiede:

  • "Quando ho lavorato su X?"

  • "Cerca nel diario Y"

  • "Trova il ticket Z"

  • "Quando ho deciso di fare W?" (cerca tipo=["chiusura"])

  • "In quali todo e' stato pianificato V?" (cerca tipo=["todo"])

Parametri:

  • query (str, required): Testo da cercare (case-insensitive, supporta regex)

  • data_inizio (str, optional): Data inizio range YYYY-MM-DD

  • data_fine (str, optional): Data fine range YYYY-MM-DD

  • ultimi_giorni (int, optional): Giorni da cercare (default 90)

  • tipo (list[str], optional): Sorgenti da cercare. Valori: "raw", "todo", "chiusura". Default: tutte e tre.

Restituisce: Lista di match con tipo (raw|todo|chiusura), data, contesto. Per i match in raw include progetto e descrizione; per todo/chiusura include il path del file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesTesto da cercare (supporta regex)
data_inizioNoData inizio YYYY-MM-DD
data_fineNoData fine YYYY-MM-DD
ultimi_giorniNoGiorni da cercare (default 90)
tipoNoSorgenti da cercare (default: tutte e tre)
Behavior5/5

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

Despite no annotations, the description fully discloses key behavioral traits: full-text search, case-insensitivity, regex support, default sources (all three), and the return format including fields for each source.

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?

The description is well-structured: begins with purpose, then features, usage examples, and parameter list. It is slightly verbose but each section adds necessary 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?

Given no output schema, the description explains the return structure in detail. All parameters are covered, and the usage examples cover typical scenarios. The tool is simple and the description is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (all parameters have descriptions), but the description adds value by explaining defaults (ultimi_giorni=90, tipo defaults to all) and providing usage context for each parameter.

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?

The description clearly states the tool searches text in diary files (raw, todo, chiusura), and among sibling tools it's the only search tool, making its purpose distinct and unambiguous.

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?

The description provides explicit examples of user queries that trigger this tool and guides on using the 'tipo' parameter to filter sources. It doesn't mention when not to use, but the context makes it clear.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mauriziomocci/mcp-cronos'

If you have feedback or need assistance with the MCP directory API, please join our Discord server