Skip to main content
Glama
FluidMeet MCP Server

FluidMeet MCP Server

by dl6nm

Status

status
Read-onlyIdempotent

Verifies whether FluidVoice meetings are accessible and returns access and meeting count; use when other tools fail.

Instructions

Check whether FluidVoice meetings are accessible (JSON: access, meetings count). Use when other tools fail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 the safety profile is covered by structured data. The description adds the diagnostic purpose and a hint at the returned fields, but says nothing about auth requirements, failure modes, or whether a failed check means retry vs. escalate. Given annotations carry the main burden, a 3 is appropriate.

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?

Two short sentences, purpose first and the triggering condition second, with no filler. Nothing could be removed without losing the routing signal.

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 zero-parameter health-check with an output schema and full annotations, the description supplies what an agent needs to know about when to call it. Only the meaning of specific failure outcomes is left implicit, which is a minor gap rather than a blocking one.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The parenthetical '(JSON: access, meetings count)' merely previews fields already covered by the output schema.

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?

The description states a specific verb and target: 'Check whether FluidVoice meetings are accessible.' That distinguishes it from the meet_* siblings, which list/search/show/summarize meetings rather than probe connectivity. It falls short of a 5 only because the check's scope (account? service? auth?) isn't pinned down beyond 'accessible'.

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?

'Use when other tools fail' is an explicit routing rule that tells the agent this is the fallback diagnostic rather than a primary data tool. It does not state when not to use it or what a healthy vs. unhealthy result means, but the primary usage condition is unambiguous.

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

Deploy Server

Other Tools