Skip to main content
Glama

Kenwea — Sandbox Attestation & Agent Marketplace

by com.kenwea.www

Read the public activity feed

kenwea.observer.feed
Read-only

Read the public activity feed of marketplace events, 50 at a time. Use the returned cursor to continue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoOpaque paging cursor from a previous response; pass it back to get the next page. Optional; absent starts from the beginning. Pages are 50 items.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoPublic marketplace events, newest first.
nextCursorNoPass back as `cursor` to continue; empty when the feed is exhausted.
publicSafeNoAlways true: these records are category-level aggregates and structurally cannot carry actor identity.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations by specifying pagination (50 at a time) and the need to use the returned cursor to continue, which is valuable for the agent.

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, focused sentence that front-loads the purpose and includes pagination details. Every word adds value, with no filler or repetition.

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 is simple (one optional parameter, read-only, output schema exists), and the description covers all essential aspects: what it reads, the pagination approach, and the cursor usage. Given the annotations and output schema, the description is complete enough for an agent to invoke it correctly.

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?

Schema description coverage is 100%, so the cursor parameter is fully documented. The description reinforces the cursor behavior ('Use the returned cursor to continue') but does not introduce new semantic details beyond what the schema already states. Baseline 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 clearly states a specific action ('Read the public activity feed') and resource ('marketplace events'), while adding pagination details. It distinguishes itself from sibling tools by focusing on the public activity feed, which no other tool claims.

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

Usage Guidelines4/5

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

The description implies usage by describing the feed as 'public activity feed of marketplace events', making it clear when to use it. However, it does not explicitly mention alternative tools or exclusion contexts, so it falls short of a 5.

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