Skip to main content
Glama

Contribuer à un défi

dandori_contribute_challenge

Ajouter ta contribution à un défi commun (par défaut, le pas prévu par le défi)

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": {
      "community_id": "<community_id>",
      "challenge_id": "<challenge_id>"
    },
    "name": "dandori_contribute_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityNoQuantité, dans l'unité du défi
challenge_idYesID du défi (voir dandori_get_community)
community_idYesID de la communauté

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description meaningfully adds that quantity defaults to the challenge's planned step when omitted, which the annotations do not convey. It still omits what a contribution does to challenge progress and what repeated calls imply despite idempotentHint=false.

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?

One short sentence with the action verb front-loaded and the default behavior tucked into a parenthetical, so nothing is wasted. The phrase 'le pas prévu par le défi' is slightly opaque, which keeps it from being maximally crisp.

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 three-parameter mutation tool with full schema descriptions and no output schema, the essentials are present, but the description says nothing about the effect of the call (progress update, validation failure, duplicate contributions). The default-value note is the only behavioral detail beyond structured fields, leaving the mutation's consequences underspecified.

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%, so the baseline is 3, but the description genuinely adds meaning the schema lacks: it explains that 'quantity' defaults to the step defined by the challenge rather than being mandatory. That resolves the ambiguity of an optional numeric parameter whose default is otherwise undocumented.

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 states a specific verb ('Ajouter ta contribution') and a specific resource ('un défi commun'), so an agent knows this records a contribution against a shared challenge rather than creating one. It never names or contrasts a sibling tool, so the boundary with tools like dandori_action or dandori_contract_progress is left to inference.

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 only implied: the word 'contribution' plus 'défi commun' suggests calling it when the user completes a challenge step, but there is no explicit when-to-use or when-not-to-use statement. No alternative tool is mentioned for the case where the user wants to create, edit, or view a challenge.

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