Skip to main content
Glama

get_effectiveness_report

Read-onlyIdempotent

Retrieve automatic effectiveness rates for injected memories—useful, neutral, harmful, and insufficient context—from recorded outcomes, optionally filtered by agent. Returns a read-only JSON summary.

Instructions

Get automatic effectiveness judgments for injected memories: useful/neutral/harmful/insufficient_context rates, judged automatically from record_outcome — independent of manual report_compliance. Optional agent_id filters the summary and limit defaults to 10. Read-only; returns JSON and does not change records.

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": "get_effectiveness_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of recent judgments in the summary (default: 10)
api_keyNoAPI key for agent authentication (required if agent has a registered key)
agent_idNoFilter by agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.11
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "API key for agent authentication (required if agent has a registered key)",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of recent judgments in the summary (default: 10)"
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/no-open-world, and the description adds meaningful context beyond them: the judgments are derived automatically from record_outcome, they are independent of manual compliance reporting, and the call does not mutate records. It returns JSON, though the shape of that JSON is not described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences that front-load the core purpose and the key differentiator from report_compliance. The trailing clause about agent_id and the limit default is redundant with the schema, which is the main wasted words.

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 carries the burden of describing returns and it does so by naming the four rate categories and the JSON format. What is missing is the broader shape of the report (time window, aggregation basis, pagination of judgments) an agent might need before relying on the numbers.

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% with per-parameter descriptions for limit, api_key, and agent_id, so the schema already does the heavy lifting. The description's notes that agent_id filters the summary and limit defaults to 10 merely restate the schema rather than adding new semantics.

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: computing automatic effectiveness judgments (useful/neutral/harmful/insufficient_context rates) for injected memories. It explicitly distinguishes itself from the manual sibling by saying it is 'independent of manual report_compliance', so an agent can route between get_effectiveness_report and get_compliance_report without opening either schema.

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 gives clear context for when this report is the right one: automatic judgments derived from record_outcome rather than manual reporting. It names the contrasting mechanism (report_compliance) but stops short of an explicit 'use X instead when...' rule or any exclusion conditions.

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