Xodia

Reply to comment

reply_to_comment

Replies on an open review thread from list_comments, as the user's AI (Xodia shows "AI for" the user). Use it to answer a question or say what you changed, in plain words for the site owner (no file paths or code). To mention a workspace member, write @Name with an id from the thread's people list; anyone else stays plain text. You can't start, resolve, reopen or delete threads: a person resolves a thread in Xodia when they are happy with it. A resolved thread refuses replies.

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": {
      "projectId": "<projectId>",
      "threadId": "<threadId>",
      "body": "<body>"
    },
    "name": "reply_to_comment"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	The reply, up to 4000 characters
`threadId`	Yes	Thread id from list_comments
`projectId`	Yes	Project id from list_projects

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only declare non-read-only, non-destructive, closed-world; the description adds real behavioral context the annotations don't carry: the reply is attributed as the user's AI ('Xodia shows "AI for" the user'), and posting fails on resolved threads. It doesn't cover failure modes beyond resolution or rate/visibility behavior, so it stops short of 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?

Front-loaded with purpose, then usage, then mention syntax, then constraints; every sentence carries information. It is dense but not padded, with only a slightly long parenthetical aside on AI attribution.

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

Completeness5/5

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

For a three-parameter mutation with no output schema, the description covers purpose, tone of the body, mention syntax, and the key failure condition (resolved thread). Nothing an agent needs to invoke it correctly is missing.

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 adds genuine semantic meaning: threadId must come from list_comments, body must be plain words for the site owner rather than file paths or code, and mentions require the @[Name](user:id) form with an id from the thread's people list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Replies on an open review thread') and grounds the resource in a sibling ('from list_comments'), so an agent can tell it apart from reply_to_request and the other write tools in the list.

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

Usage Guidelines5/5

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

Gives explicit when-to-use cases ('answer a question or say what you changed') plus explicit when-not: can't start, resolve, reopen or delete threads, and a resolved thread refuses replies. It also names who does the alternative action (a person resolves a thread in Xodia).

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

All Xodia tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?