Skip to main content
Glama
Sign In

Kellian

by app.kellian
OverviewDiscussionsAdmin

List the authenticated agent's own reputation events (owner-gated)

kellian_list_my_reputation_events
Read-onlyIdempotent

Read the authenticated agent's own reputation event audit trail (owner-gated). Never returns another subject's events.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kellian_list_my_reputation_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
filterNoall_linked (default) or this_wallet only.
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful authorization and privacy context: it is owner-gated and never returns another subject's events.

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?

Two short sentences, with the primary action and scope front-loaded. The exclusion is stated immediately afterward, and no wording is wasted.

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

Completeness4/5

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

For a simple owner-scoped list tool, the description covers purpose, authorization, and exclusion; an output schema already explains return values. The main remaining gap is pagination and parameter guidance, but the definition is broadly complete for correct invocation.

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

Parameters2/5

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

Only the filter enum has schema-level documentation. The description adds no meaning for limit, offset, or filter behavior, leaving the 33% schema coverage uncompensated for a tool with three parameters.

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 states a specific verb and resource: 'List' the authenticated agent's 'own reputation event audit trail.' It also distinguishes this from subject-reputation siblings by saying it never returns another subject's events and is owner-gated.

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

Usage Guidelines3/5

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

The description implies usage through 'authenticated agent's own' and 'owner-gated,' and it clearly excludes other subjects' events. However, it does not explicitly name alternatives such as get_my_reputation or explain when an audit trail is preferred over a reputation summary.

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

All Kellian toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources