Skip to main content
Glama
Sign In
atomicreps

atomicreps

Official
by atomicreps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

How the user is doing

me

View your atomicreps progress as a block, including summary, skills, reps, streak, and mutes, to track retrieval-practice performance.

Instructions

How the user is doing: summary, skills, reps, streak, or mutes, as a block.

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

Input Schema

NameRequiredDescriptionDefault
showNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It only says the result is 'as a block,' which hints at an aggregate return but omits read/write safety, authentication needs, side effects, or whether 'show' filters or selects.

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?

A single short sentence with no filler. It is appropriately sized for a simple tool, though the leading title-like phrase is somewhat redundant.

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

Completeness2/5

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

Given no annotations, no output schema, and 0% schema coverage, the description is incomplete. It should clarify how 'show' works and what the block contains, but leaves key invocation details unstated.

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 0% and the single 'show' parameter is undocumented in the schema. The description implicitly lists likely values (summary, skills, reps, streak, mutes), adding useful meaning, but it does not state that these are the accepted values, nor does it cover defaults or format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists the data categories returned (summary, skills, reps, streak, mutes) but does not use a specific verb or clearly differentiate from siblings rep, answer, and settings. An agent can infer it retrieves a user profile block, but the purpose is not sharply stated.

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

Usage Guidelines2/5

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

No when-to-use guidance, no exclusions, and no mention of alternatives like rep or settings. The agent must guess that this is the general user overview tool.

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

Deploy Server

Other Tools