Skip to main content
Glama

parabol

by io.usefulapi

Create a reflection

create_reflection
Destructive

MUTATES Parabol data: add a reflection card to a running retrospective's reflect phase. Required: meetingId, promptId (the reflect-prompt/column), sortOrder (Float). content (optional) is a stringified TipTap/ProseMirror JSON document (<=2000 chars). Parabol GraphQL: createReflection(input). Requires MEETINGS_WRITE.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoAdditional documented GraphQL input fields to send verbatim in this mutation's input (merged OVER the typed fields above).
contentNoReflection text as a stringified TipTap/ProseMirror JSON document.
promptIdYesThe reflect-prompt (column) id (required).
meetingIdYesThe retrospective meeting id (required).
sortOrderNoSort order within the column (Float). Defaults to 0.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark destructiveHint=true, and the description reinforces this with 'MUTATES' and the required MEETINGS_WRITE permission. It also discloses the GraphQL mutation endpoint and content length constraint, adding useful behavioral context beyond the annotation.

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 tightly packed, front-loads the mutation intent, and every sentence contributes: purpose, required inputs, content constraints, endpoint, and permission. There is no filler or redundancy.

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

Completeness3/5

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

It provides the core invocation details, endpoint, and permission, but the sortOrder 'required' conflict with the schema is a meaningful gap. With no output schema, a brief note on the response shape would have made it more complete.

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 coverage is 100%, so the baseline is 3. The description adds meaningful details like content being a stringified TipTap/ProseMirror document up to 2000 chars and sortOrder being a Float, but it incorrectly lists sortOrder as required while the schema does not mark it required.

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 states a specific action ('add a reflection card'), a specific resource ('a running retrospective's reflect phase'), and confirms it mutates Parabol data. This clearly differentiates the tool from siblings like create_task or add_comment.

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

Usage Guidelines4/5

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

It gives clear context for when to use the tool: adding a reflection to a running retrospective's reflect phase. It also includes a permission requirement (MEETINGS_WRITE) but does not explicitly name alternatives or state when not to use it.

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

All parabol toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Every tool targets a distinct resource and action: get_/list_ tools are clearly separate read paths, create_/update_/start_/add_ tools map to distinct mutations, and the two escape hatches are explicitly labeled. Even near neighbors like list_meetings and list_active_meetings are unambiguous.

Naming Consistency4/5

Most tools follow a consistent pattern: list_/get_ for reads, create_/update_/start_ for mutations, with plural nouns for collections and singular for single resources. Minor deviations like add_comment, invite_to_team, and the parabol_* escape hatches prevent a perfect score.

Tool Count3/5

With 21 tools, the server sits in the 16-25 range that feels heavy for an MCP surface. The breadth is somewhat justified because Parabol spans organizations, teams, meetings, tasks, and comments, but many tools are list/get variants of the same core entities.

Completeness3/5

Core read and write flows exist for teams, organizations, meetings, tasks, and comments, but there are notable lifecycle gaps such as no delete_task, no reflection update/delete, and no meeting end/update mutations. The parabol_graphql and parabol_query escape hatches help work around these gaps but do not make the curated surface fully complete.

Resources