Skip to main content
Glama
TrialRun MCP

TrialRun MCP

by kostadindev

AI literacy report

get_report

Generates a markdown report to review an agent's data stewardship score, restricted-data counts by type and channel, files read, and three recent habit examples.

Instructions

A short markdown report for the user: data stewardship score, restricted data by type and channel (counts only, no values), files read, and the three habits with recent examples.

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_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful traits: output format is markdown, the report is 'short', and restricted data is reported as counts only with no values (a privacy constraint an agent should not try to work around). It omits any statement about read-only behavior, permissions, cost, or what happens when there is no activity to report.

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?

One sentence, front-loaded with the output format and then the section list; every clause adds information and there is no filler. A slightly tighter structure (e.g., separating format from contents) would be marginal gain only.

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 zero-parameter, read-only aggregation tool with no output schema, the section enumeration tells the agent exactly what to expect back, which is the main missing piece. Remaining gaps are edge behavior: empty-state output and whether the report is user-scoped or global.

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

Parameters4/5

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

The tool takes zero parameters and the schema has no properties, so there is nothing parameter-level to explain; baseline 4 applies. The description correctly does not invent parameter claims.

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?

The description names the concrete artifact (a short markdown report) and enumerates its sections: stewardship score, restricted data by type/channel, files read, and three habits with recent examples. That is specific enough to distinguish it from raw-data siblings like get_audit_log or list_files, though it never states the action verb (generate/return) explicitly.

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: the phrase 'for the user' and the aggregate nature suggest this is the presentable summary rather than raw records, which hints at when to pick it over get_audit_log. No explicit when-to-use, prerequisites, or named alternatives are given.

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