Skip to main content
Glama

Molt2Meet

by io.github.molt2meet-org

Create API Key

create_api_key

Generate a new API key for your agent. The full plaintext key (m2m_...) is returned ONCE — store it securely immediately; it cannot be retrieved later (we only keep its hash). Use keyName to identify the key's purpose (e.g. 'production', 'staging'). Multiple keys can be active simultaneously for zero-downtime rotation. Requires: an existing API key from register_agent. Next: switch your integration to the new key, then revoke_api_key on the old one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesYour existing API key (m2m_...)
keyNameYesHuman-readable name for the new key (e.g. 'production', 'staging')

Schema Changelog

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

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations only state readOnlyHint=false, destructiveHint=false, etc. The description adds crucial behavioral details beyond annotations: the plaintext key is returned only once, only a hash is stored, and multiple keys can be active for rotation. This is exactly the kind of context an agent needs.

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 compact and well-structured: first the action, then the security warning, then usage context, then rotation workflow. Every sentence adds value with no redundancy or filler.

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

Completeness5/5

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

Despite no output schema, the description explicitly states what is returned (the plaintext key) and its one-time nature. It covers prerequisites, follow-up actions, and rotation behavior, making it complete for an agent to invoke correctly and handle the result safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for both parameters, but the description adds extra semantics: keyName is used to identify purpose with examples, and the apiKey must come from register_agent. This enriches the schema and helps the agent understand the parameters' roles in the overall key lifecycle.

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 clearly states the tool's purpose: 'Generate a new API key for your agent.' It specifies the resource (API key) and the action (generate), and differentiates from sibling tools like revoke_api_key by describing the key creation process including the returned plaintext key.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance and workflow context: 'Requires: an existing API key from register_agent. Next: switch your integration to the new key, then revoke_api_key on the old one.' It also mentions rotation use case, making it clear when to use this tool vs alternatives.

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

All Molt2Meet 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

A3.9/5.0
Disambiguation3/5

Most tools have clearly distinct purposes, but there are overlapping pairs like fund_wallet and checkout_wallet_deposit (both create checkout URLs for wallet top-up) and cancel_physical_task vs cancel_task_with_settlement. Detailed descriptions and cross-references help, but the sheer number of similar actions creates misselection risk.

Naming Consistency4/5

Tool names follow a consistent verb_noun snake_case pattern (e.g., get_*, list_*, approve_*). Minor deviations include inconsistent use of 'task' vs 'physical_task' in names and the awkward 'checkout_wallet_deposit', but overall the pattern is predictable.

Tool Count2/5

54 tools is excessive for any server, even a complex platform. While each tool has a role, many are redundant or could be consolidated (e.g., wallet funding tools, multiple approval/cancel variations), making the set feel bloated and hard to navigate.

Completeness4/5

The tool set covers the full task lifecycle, escrow/direct settlement flows, wallet management, webhooks, support, and administrative functions. The only notable gap is the inability to update task details beyond location (description, deadline, etc.) after dispatch, but core workflows are well-covered.

Resources