create_guest
Creates a guest mr_…
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
meta-agent-tools
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden of behavioral disclosure. It states that a guest is created, but gives no indication of side effects, required permissions, idempotency, or response behavior. The odd 'mr_…' suffix adds confusion rather than clarity.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short and begins with the core action, which is structurally efficient. However, 'mr_…' is an unexplained fragment that seems cut off, so the brevity comes at the cost of clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Although the tool is simple and has no parameters, the description leaves important context missing: what a guest is in this system, what 'mr_…' means, and how this relates to the surrounding billing, contact, and listing tools. The description is not complete enough for an agent to invoke the tool with confidence.
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 input schema has zero properties and schema description coverage is trivially 100%, so there are no parameters to explain. Per the baseline for zero-parameter tools, the description does not need to provide parameter semantics.
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 clearly identifies the action and resource: 'Creates a guest'. The verb is specific and the resource is distinct from sibling tools like create_listing. However, the trailing 'mr_…' is cryptic and appears truncated, preventing a fully unambiguous understanding.
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?
There is no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The tool name implies it is for creating a guest, but the description does not provide any decision-making context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.6/5.0
Disambiguation4/5
Most tools target distinct resources or actions, and descriptions are clear enough to avoid major confusion. The main overlap is between list_listings and list_mcp_servers as registry views, though their scope differs.
Naming Consistency3/5
The set mixes verb_noun names like create_listing and list_comments with noun-style names like api_index, billing, contact, and health. This is readable but not a consistent naming convention across the whole server.
Tool Count5/5
Twelve tools is a reasonable, well-scoped count for a registry-and-commerce server. Each tool has a distinct role, with no obvious bloat or redundancy.
Completeness3/5
Discovery, creation, liking, and commenting are covered, but there are no update or delete operations for listings, nor any comment management beyond listing comments. These are notable lifecycle gaps for a registry-style tool.