Skip to main content
Glama

Lister les contacts

dandori_list_contacts
Read-onlyIdempotent

Lister les contacts, ceux à recontacter en premier. Pour la fiche complète et l'historique des échanges : fetch avec contact:ID

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

Input Schema

NameRequiredDescriptionDefault
tagNoFiltrer par tag (nom)
searchNoTexte cherché dans le nom, le surnom ou la relation
overdueNotrue : seulement ceux à recontacter
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond them: results are ordered with priority recontacts first, and the returned data is summary-level only, without full profile or exchange history. No pagination or result-size behavior is disclosed.

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 short sentences with zero filler: listing scope and ordering first, then the pointer to the alternative tool. Everything is front-loaded and each clause earns its place.

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

Completeness4/5

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

For a four-optional-parameter, no-output-schema list tool with full annotation coverage, the description supplies purpose, ordering and a delegation path to fetch. Minor gap: nothing about how many contacts are returned or whether filters combine, but nothing essential to a correct call 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 75%, so tag, search, overdue and the category enum are mostly documented in the schema itself. The description only implicitly touches the priority concept ("à recontacter") and adds no syntax guidance for search matching or tag naming; the baseline 3 applies since the schema carries the load.

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?

States a specific verb and resource ("Lister les contacts") plus the ordering rule "ceux à recontacter en premier", so the agent knows this is a read-only contact listing sorted by recontact priority. It also names the boundary against the sibling "fetch" for full records, though it does not cover the other list_* siblings.

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?

Explicitly routes the agent: use this tool to list contacts, and use "fetch avec contact:ID" when the full record and exchange history are needed. That is a clear use/use-something-else split. It stops short of saying when filtering (overdue/tag/category) is preferable, leaving that to the schema.

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