Skip to main content
Glama

Rechercher dans Dandori

dandori_search
Read-onlyIdempotent

Recherche globale par texte (2 caractères au moins) : tâches, projets, objectifs, notes, listes, contrats, routines, envies, dates importantes, contacts, lectures, capture, maison, abonnements, tags. Jamais le journal, et seulement les modules que l'utilisateur a ouverts à l'IA. Renvoie les résultats groupés par type, avec leurs ID

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": "dandori_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTexte à rechercher

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is low, yet the description adds genuinely new behavior: a permission-based scope limit (only AI-enabled modules), a permanent exclusion (journal), and the response shape (grouped by type, IDs included). An agent knows in advance why it might get zero results and how to consume the output.

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?

Front-loads the core action and the minimum-length rule, then the scope, then the return format — good ordering. The 15-item module enumeration is long but each item earns its place by defining the searchable surface, so it stays efficient rather than padded.

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 single-parameter read tool with full annotation coverage and no output schema, the description supplies everything an agent needs: input constraint, permission-dependent coverage, explicit exclusion, and result structure. Nothing material 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 coverage is 100% and the single `query` parameter is fully documented with its minLength, so the schema does the heavy lifting and baseline 3 applies. The description only reinforces that the input is raw text matched across modules (no field-scoped syntax), which is marginal added meaning.

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?

Names a specific verb and resource ("Recherche globale par texte") and then enumerates the exact entity types covered, which makes clear this is the cross-cutting search rather than a per-module read tool like dandori_get_list_items. The closing statement about grouped-by-type results further pins down what the tool is.

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 precondition (2 characters minimum) and two hard exclusions — never the journal, and only modules the user has opened to the AI — which tell the agent when results will be empty or incomplete. It stops short of naming an alternative tool or contrasting itself with the sibling "search", so it is clear context without explicit routing.

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