Skip to main content
Glama
Sign In

kit-memory-demo

by io.github.PeterAtPondo
OverviewDiscussionsAdmin

kit_ranking_compare

ranking_compare

Compare search ranking for a query with and without the recently learned boost. Returns every row whose rank or score changes, with baseline rank, boosted rank, position delta, score delta, sample source, boost window, and units.

Input Schema

NameRequiredDescriptionDefault
tierNoOptional memory tier filter
limitNoMax candidate rows to compare, default 50 and capped by the API at 100
queryYesSearch query to compare over the real caller-scoped memory sample
projectNoOptional project filter
surfaceNoOptional surface filter
categoryNoOptional memory category filter
kit_session_idNoYour own session ID from wake; reuse for this conversation. A child or subagent must wake separately, without its parent's ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • addedInput schema / properties / kit_session_id
      Added value: +{
+  "description": "Your own session ID from wake; reuse for this conversation. A child or subagent must wake separately, without its parent's ID.",
+  "maxLength": 160,
+  "minLength": 8,
+  "pattern": "^[A-Za-z0-9:_-]+$",
+  "type": "string"
+}
  3. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations carry only a title, so the description must carry the behavioral load. It does disclose the key filtering behavior ('returns every row whose rank or score changes') and the per-row payload (baseline rank, boosted rank, deltas, sample source, boost window, units), which is genuinely useful. It does not say whether the call is read-only, how expensive it is, or how it behaves when no boost has been learned.

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 sentences with zero filler; the comparison is front-loaded and the return shape follows immediately after. Nothing repeats the name or title.

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?

With no output schema, the description correctly enumerates the returned row fields, and all parameters are covered by the schema. What is missing is the precondition and failure mode (no learned boost, empty sample), which matters for an agent deciding whether the call is meaningful.

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 coverage is 100%, so all seven parameters are already documented in the schema, including the limit cap and the kit_session_id rules. The description adds no meaning beyond that and mentions only 'units', which is not a parameter. Baseline 3 applies.

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?

States a specific verb and resource ('Compare search ranking for a query') plus the exact comparison basis (with vs. without the recently learned boost). No sibling in the list does ranking comparison, so no disambiguation is needed.

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?

Usage is only implied: an agent can infer this is a diagnostic for verifying boost effect, but the description never says when to reach for it versus recall, or what precondition (an existing learned boost / active session from wake) must hold.

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

All kit-memory-demo toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources