Skip to main content
Glama

Record shown, confirmed or rejected insights

record_insight_feedback

Records what a person did with insights from get_reading_plan so its scoring can be learned later. Stores only claim ids, claim kinds and the reaction (shown, confirmed, rejected); never text or birth details. Needs an API key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "events": "<events>"
    },
    "name": "record_insight_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventsYes

Output Schema

NameRequiredDescriptionDefault
statusYes
storedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-open-world write, so the description doesn't need to restate safety. It adds genuinely new behavior: data minimization ("never text or birth details") and an auth prerequisite ("Needs an API key"). It omits the one thing the non-idempotent annotation implies – whether re-posting the same claims creates duplicate events – which keeps it from a 5.

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?

Three short sentences, each doing distinct work: what it does and why, exactly what is persisted, and the auth requirement. Purpose is front-loaded and there is no redundant restatement of the title or annotations.

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?

An output schema exists, so return values need no explanation, and the privacy and auth notes cover the main non-obvious risks of a write tool. What's missing is the duplicate/repeat-submission behavior implied by idempotentHint=false and any indication of what rank and topic are for within an event.

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 0%, so the description carries the burden of explaining parameters, and it only partly does: it names claim ids, claim kinds, and the reaction enum values (shown, confirmed, rejected), which maps to three of the five item fields. The rank (1-3) and topic fields are never mentioned, and the batch nature (up to 24 events) is left entirely to the schema.

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?

"Records what a person did with insights from get_reading_plan" names a specific verb (records), a specific resource (user reactions to insights), and a downstream reason (scoring can be learned later). The scope is unmistakable. It does not explicitly separate itself from the other record_* siblings (record_consultation_outcome, record_prashna_outcome), so it stays at 4 rather than 5.

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?

It ties the call to a concrete moment: after a person has seen insights produced by get_reading_plan. That is a real when-to-use cue rather than an implied one. There is no when-not guidance (e.g., not for consultation outcomes, which have their own tools), 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources