Skip to main content
Glama
Sign In

Fuzzbucket AI

by ai.fuzzbucket.api
OverviewDiscussionsAdmin

Read workspace chat

fuzz_read_chat
Read-onlyIdempotent

Returns persisted user and assistant messages from a workspace chat conversation, with pagination.

Input Schema

NameRequiredDescriptionDefault
pageNoOptional bounded page size and cursor; follow the returned cursor for more results.
workspaceIdYesWorkspace ID returned by fuzz_list_workspaces or fuzz_create_workspace. Resources must belong to this workspace.
conversationIdYesWorkspace chat conversation ID returned by fuzz_send_chat_message or fuzz_get_workspace. Where it is optional, omitting it starts a new conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / conversationId
      Added value: +{
+  "description": "Workspace chat conversation ID returned by fuzz_send_chat_message or fuzz_get_workspace. Where it is optional, omitting it starts a new conversation.",
+  "maxLength": 255,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / page / properties / cursor / description
      Previous value: -"Opaque pagination/event cursor returned by the previous response. Omit for the first page."New value: +"Opaque pagination cursor returned by the previous response. Omit for the first page."
    • removedInput schema / properties / sessionId
      Removed value: -{
-  "description": "Chat or onboarding session ID returned by an earlier call. Where it is optional, omitting it starts a new session.",
-  "maxLength": 255,
-  "minLength": 1,
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "workspaceId",
-  "sessionId"
-]New value: +[
+  "workspaceId",
+  "conversationId"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / sessionId / description
      Previous value: -"Chat or onboarding session identifier returned by the corresponding tool. Omit on a new send/create when no session exists."New value: +"Chat or onboarding session ID returned by an earlier call. Where it is optional, omitting it starts a new session."
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds only that messages are 'persisted' and paginated; it does not say whether empty conversations error, how ordering works, or what the cursor contract implies beyond the schema's own text.

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?

A single, front-loaded sentence with no filler; the resource and the pagination trait appear immediately.

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 list tool with full parameter documentation and annotations covering safety, the description is close to sufficient, and it indicates what is returned (user and assistant messages). It lacks any note on message ordering or what a page of results looks like, which matters slightly since there is no output schema.

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%, including detailed notes on limit bounds and cursor usage, so the baseline is 3. The description contributes nothing beyond reiterating pagination, which the schema already explains thoroughly.

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 ('Returns') and resource ('persisted user and assistant messages from a workspace chat conversation'), plus the pagination trait. It clearly is not a mutation or a workspace listing, so an agent can separate it from siblings like fuzz_get_workspace, though it does not name those siblings explicitly.

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?

There is no explicit statement of when to use this versus alternatives such as fuzz_get_workspace (which the schema notes also returns conversation IDs) or message-sending tools. The only usage-like hint is the pagination mention, which is really a behavioral note rather than routing guidance.

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

All Fuzzbucket AI toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources