Skip to main content
Glama
franccesco

Bloomy MCP

by franccesco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_query_detailsA

Get detailed information about specific GraphQL queries.

Retrieves argument requirements, return type information, descriptions, and
example usage for the specified queries.

Args:
    query_names: Comma-separated list of query names to get details for

Returns:
    A YAML-formatted string containing detailed information about the requested queries
get_mutation_detailsA

Get detailed information about specific GraphQL mutations.

Retrieves argument requirements, return type information, descriptions, and
example usage for the specified mutations.

Args:
    mutation_names: Comma-separated list of mutation names to get details for

Returns:
    A YAML-formatted string containing detailed information about the requested mutations
execute_queryA

Execute a GraphQL query or mutation with variables.

Parses and executes the provided GraphQL operation string with optional variables.

Args:
    query: Raw GraphQL query or mutation string
    variables: Optional dictionary of variables to use in the operation

Returns:
    Dictionary containing the operation results or an error message string

Raises:
    Exception: Handled internally, returns error message as string
get_authenticated_user_idA

Get the ID of the currently authenticated user.

Uses a special mutation to retrieve the ID of the user associated with
the current API token.

Returns:
    User ID string if successful, None if user not found, or error message string

Raises:
    Exception: Handled internally, returns error message as string

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
bloom://queries
bloom://mutations
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: execute_query performs operations, get_authenticated_user_id handles authentication, and get_mutation_details/get_query_details provide metadata. The two detail tools are differentiated by query vs mutation focus, preventing confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern with snake_case: execute_query, get_authenticated_user_id, get_mutation_details, get_query_details. The pattern is predictable and readable throughout the set.

Tool Count5/5

Four tools is well-scoped for a GraphQL-focused server: one for execution, one for authentication, and two for schema introspection. Each tool earns its place without bloat or thin coverage for the domain.

Completeness4/5

The surface covers core GraphQL workflows well: execution, authentication, and schema details for both queries and mutations. A minor gap is the lack of a tool for subscription details or general schema exploration beyond specific queries/mutations, but agents can work around this.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources