Code-Fundi MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

code-fundi-conversation

Read-only

Retrieve all messages in a conversation thread by its ID to access the full discussion history for codebase analysis and impact review.

Instructions

Get all messages in a conversation thread by its conversation ID.

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "code-fundi-conversation"
  }
}

Input Schema

Name	Required	Description	Default
`conversation_id`	Yes	Conversation thread UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jul 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The readOnlyHint annotation already declares a safe read operation, and the description aligns perfectly. The description adds the specific scope of 'all messages in a conversation thread', but does not disclose any additional behavioral aspects such as ordering, pagination, or potential size limits. With annotations covering the safety profile, this is adequate but not enriched.

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

Conciseness5/5

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

The description is a single sentence that is direct and immediately understandable. It front-loads the action and resource, with no redundant words or filler. Every word serves a purpose.

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 simple read-only tool with one parameter and no output schema, the description sufficiently describes what the agent will get ('all messages in a conversation thread'). It does not explain the return format or pagination, but such details are not critical for basic invocation given the low complexity. The description is complete enough to select and use the tool.

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%: 'conversation_id' is documented as 'Conversation thread UUID'. The description only restates this as 'conversation ID', adding no new semantic meaning. The parameter is simple and fully explained by the schema, so the baseline of 3 applies.

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?

The description clearly states the action ('Get all messages') and the resource ('conversation thread'), with a specific lookup key ('conversation ID'). It is distinct from siblings by focusing on retrieving messages from an existing conversation, unlike chat (which sends) or history tools likely listing conversations.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. For example, it does not mention that this should be used after obtaining a conversation ID, nor does it differentiate from 'history-item' or 'list-history'. The description tells what it does but not when it is the right choice.

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