Skip to main content
Glama
Sign In

Dandori

by life.dandori
OverviewDiscussionsAdmin

Créer un contrat

dandori_create_contract

Créer un contrat d'engagement : un objectif tenu chaque semaine, que des témoins valident. Sans Plus, le nombre est limité (le refus le dit).

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": {
      "title": "<title>",
      "deadline": "<deadline>"
    },
    "name": "dandori_create_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoNoms des tags
stakeNoCe qui est en jeu si l'engagement n'est pas tenu
titleYesL'engagement, en une phrase
deadlineYesDate de fin (YYYY-MM-DD), après aujourd'hui
witnessesNoTémoins à inviter. Sans Plus, aucun e-mail ne part : partage leur lien d'invitation (voir dandori_get_contract)
descriptionNoLe détail de l'engagement
weekly_targetNoNombre de fois par semaine (1 à 7)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent creation. The description adds one genuine piece of behavior beyond that: free accounts hit a limit on the number of contracts and the refusal reports it. It says nothing about side effects (invitations sent, confirmation step) or what a successful creation yields.

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?

Two compact sentences, front-loaded with the core definition, with no filler. The trailing parenthesis '(le refus le dit)' is slightly cryptic and does little work, but the overall density is appropriate for a short description.

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

Completeness3/5

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

For a 7-parameter mutation with no output schema, the description covers what a contract is and the quota behavior, and the schema handles parameter detail. It is still missing what the caller gets back (contract identifier or invitation links) and whether creation has any confirmation or notification side effects.

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 every parameter already carries its own explanation, including the free-tier e-mail caveat for witnesses. The description adds no parameter-level meaning beyond the schema, which is the expected baseline here.

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?

The description gives a specific verb and resource ('Créer un contrat d'engagement') and explains the concept: a weekly goal validated by witnesses. That conceptual definition helps distinguish it from the sibling create_* tools such as dandori_create_goal, though it never explicitly contrasts them.

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

Usage Guidelines3/5

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

Usage is implied by the concept (a commitment validated by witnesses, with a weekly target), and the free-tier constraint is stated. However, there is no explicit when-to-use vs. when-to-use-an-alternative guidance, e.g. contract versus goal or versus the contract add/update siblings.

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

All Dandori toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources