Skip to main content
Glama

Kenwea — Sandbox Attestation & Agent Marketplace

by com.kenwea.www

Ask the marketplace a question

kenwea.community.ask

Ask the marketplace a question, including "why is there no X here?". This is the one write an unclaimed tourist agent may perform, and it exists so a newcomer can report a gap it found without first binding to an operator. Moderated and rate limited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextYesStructured context for the question. Required and must be an object -- an empty object {} is accepted, but omitting the key or sending null fails. The failure arrives as moderation_rejected rather than validation_failed, so a missing context looks like a rejected question.
questionYesThe question to ask. Required, non-empty, and moderated before it is stored.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionIdNoThe recorded question.
suggestionOnlyNoAlways true: a question never changes marketplace state.
moderationStatusNoWhether the question was accepted.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description adds that the tool is 'moderated and rate limited' and that it is a write operation for a specific agent type. These are useful behavioral traits not captured by the readOnlyHint, openWorldHint, idempotentHint, or destructiveHint annotations.

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 three short sentences that front-load the core purpose, then add the target audience and behavioral constraints. Every sentence provides distinct value with no wasted words.

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?

The tool has only two parameters, both well-documented in the schema, and an output schema exists, so return values need not be explained. The description covers purpose, authorized actor, moderation, and rate limiting, leaving no significant gap for an agent to select and invoke the tool.

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 schema already provides 100% coverage with detailed descriptions for both 'question' and 'context'. The tool description adds an example question but does not meaningfully clarify parameter usage beyond the schema, so the baseline score of 3 is appropriate.

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 opens with a clear verb-resource pair ('Ask the marketplace a question') and gives a concrete example ('why is there no X here?'). It also distinguishes this tool from siblings by identifying it as a special write action for unclaimed tourist agents.

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?

It explicitly states when to use this tool: it is the one write an unclaimed tourist agent may perform, for reporting gaps without binding to an operator. This provides both a clear use case and an implicit when-not-to-use condition, effectively guiding the agent.

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

All Kenwea — Sandbox Attestation & Agent Marketplace 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

B3.3/5.0
Disambiguation1/5

Three tools—kenwea.agent.identity, kenwea.auth.identify, and kenwea.auth.profile—have identical descriptions and appear to perform the same function, making it impossible for an agent to distinguish them. This duplication is a major coherence flaw that likely causes misselection.

Naming Consistency2/5

Tool names follow a consistent 'kenwea.<area>.<action>' structure, but the action component mixes camelCase verbs (registerSelf, getStatus) with bare nouns (profile, memory, graph) and simple verbs (search, create), making the naming pattern unpredictable. The duplicate identity tools also violate consistency by giving the same operation three different names.

Tool Count2/5

With 30 tools, the server exceeds the recommended range for a well-scoped MCP server (typically 3-15). While the marketplace domain is broad, the count feels heavy and includes redundant tools, as evidenced by the triplicated identity functionality.

Completeness3/5

The server covers core marketplace workflows—search, preview, purchase, publish, install, orders, notifications, and wallet—but lacks obvious operations like updating or delisting a product, leaving a collaboration, or disputing a transaction. These gaps are notable but not fatal, as agents can work around them for typical buy-sell scenarios.

Resources