Skip to main content
Glama

Détail d'une communauté

dandori_get_community
Read-onlyIdempotent

Voir une communauté, ses défis communs et ses membres (leur ID sert à une demande d'ami)

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": {
      "id": "<id>"
    },
    "name": "dandori_get_community"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID de la communauté

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds value beyond that by disclosing the shape of the result (community, shared challenges, member list) and the reusable nature of member IDs. It does not mention pagination or access constraints, which keeps it from a 5.

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?

A single front-loaded sentence with the resource first and the payload details after. The parenthetical earns its place by explaining the practical use of member IDs. Slightly informal phrasing ('Voir') is the only minor weakness.

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 one-parameter read tool with no output schema, the description does the important work of telling the agent what comes back (community, challenges, members) and why the member IDs matter. With annotations covering safety, nothing critical is missing; only pagination/volume expectations are unaddressed.

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?

There is a single required parameter with 100% schema description coverage ('ID de la communauté'), so the schema already carries the semantics. The description adds no format, range, or sourcing guidance for the id — the only 'ID' it mentions refers to member IDs in the response, not the input. Baseline 3 applies.

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 ('Voir une communauté') and then enumerates what the payload contains: shared challenges ('défis communs') and members. That is far more informative than the title alone. It does not explicitly contrast itself with sibling getters like dandori_get_contract or dandori_get_project, so it stops short of a 5.

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 parenthetical notes that member IDs are meant for a friend request, which hints at a downstream workflow. There is no explicit statement of when to choose this tool over a sibling or any prerequisite/exclusion. An agent can infer the use case but is not routed.

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