concordance

group_contribute

[KEEP · internal] Add a verse/note/question to a group's shared study — attributed to your handle, optionally signed. Verbatim; a member's own words, not engine-verified.

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>",
      "text": "<text>"
    },
    "name": "group_contribute"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`kind`	No
`refs`	No
`text`	Yes
`handle`	No
`topics`	No
`subject_id`	No
`attestation`	No	optional: sign sha256(text) with your own key (signing.sign_seal) and pass it here — a handle alone is only a claim, a signature makes your authorship checkable. Never send a private key.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedAug 4, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / attestation / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / handle / maxLength
```
Added value: +4000
```
- addedInput schema / properties / id / maxLength
```
Added value: +4000
```
- addedInput schema / properties / kind / maxLength
```
Added value: +4000
```
- addedInput schema / properties / refs / items
```
Added value: +{
+  "maxLength": 4000,
+  "type": "string"
+}
```
- addedInput schema / properties / refs / maxItems
```
Added value: +200
```
- addedInput schema / properties / subject_id / maxLength
```
Added value: +4000
```
- addedInput schema / properties / text / maxLength
```
Added value: +4000
```
- addedInput schema / properties / topics / items
```
Added value: +{
+  "maxLength": 4000,
+  "type": "string"
+}
```
- addedInput schema / properties / topics / maxItems
```
Added value: +200
```

Changed1 schema field changedJul 28, 2026

addedInput schema / properties / attestation

Added value: +{
+  "description": "optional: sign sha256(text) with your own key (signing.sign_seal) and pass it here — a handle alone is only a claim, a signature makes your authorship checkable. Never send a private key.",
+  "type": "object"
+}

Changed1 schema field changedJul 28, 2026
- removedInput schema / properties / private_key
```
Removed value: -{
-  "type": "string"
-}
```
First observedJul 8, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden but only partially delivers: it discloses that content is attributed to the caller's handle, optionally signed, and explicitly not engine-verified ('verbatim; a member's own words'). It omits whether membership is required, whether contributions are reversible/editable, and what happens on success.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Compact and reasonably front-loaded — the core action leads and the qualification about verification follows. However, the '[KEEP · internal]' tag is unexplained jargon that spends characters without clarifying behavior.

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

Completeness2/5

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

A mutation tool with no annotations, no output schema, 8 parameters at 13% coverage, and a nested attestation object. The description should compensate for the missing structured guidance (membership, mutability, param meanings) but does not, leaving key operational context absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13%, so the description must compensate. It explains handle (attribution) and, via 'optionally signed', gestures at attestation, but leaves kind, refs, topics, subject_id, and id entirely undocumented — the majority of 8 parameters carry no meaning in either place.

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 (add) and resource (verse/note/question to a group's shared study), which distinguishes it from sibling group tools like group_create, group_join, and group_get. It does not explicitly name an alternative it is not, but the purpose is unmistakable.

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?

The '[KEEP · internal]' marker hints this is an internal/supported tool and context implies contribution to an existing group study, but there is no explicit when-to-use vs alternatives (e.g., study_import or mesh_post) nor any stated prerequisites such as group membership.

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

All concordance tools Inspect

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.