Skip to main content
Glama
Sign In
FireKey MCP Server

FireKey MCP Server

by partnerhbhl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

group_create

Create a new browser profile group for organizing profiles. Provide a group name and optional remark to set up a group for better profile management.

Instructions

Create a new profile group.

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": {
      "group_name": "<group_name>"
    },
    "name": "group_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
remarkNoGroup description
group_nameYesName for the new group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that a new group is created, omitting important behavior such as duplicate name handling, permissions required, side effects on existing profiles, or what the response contains.

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 efficient sentence with no filler. The action and resource are front-loaded, making it appropriately sized for such a simple tool.

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?

For a two-parameter create tool, the schema and description are sufficient for basic invocation. However, the lack of output schema and behavioral details leaves gaps, such as what happens on duplicate group names and what data is returned after creation.

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?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds no additional parameter meaning beyond the schema, but no compensation is needed given full schema coverage.

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 'Create a new profile group' uses a specific verb and resource, making the tool's purpose immediately clear. It naturally differentiates from sibling tools like group_list and group_update, which cover listing and updating groups.

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 on when to use this tool versus alternatives such as profile_create or group_update. There are no prerequisites, exclusions, or conditions stated, so the agent must infer usage entirely from the name and minimal description.

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