Skip to main content
Glama

Diastella

System history

system_history
Read-onlyIdempotent

Everything remembered about one system of a project: its most recent past failures with their fixes and the files those fixes changed, who wrote the fixes, who has changed the system most, what depends on it and what it depends on. system is a name from project_memory.

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": {
      "repository": "<repository>",
      "system": "<system>"
    },
    "name": "system_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
systemYes
repositoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world operation. The description adds meaningful behavioral context by explaining what information is returned: recent failures, their fixes, changed files, authors, change frequency, and dependency relationships.

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?

The description is front-loaded with a clear summary and then enumerates the kinds of history returned. It is somewhat dense, but the details are relevant and no sentence is clearly wasted.

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 read-only history tool with no output schema, the description does a good job explaining the scope and contents of the result. The main gap is the unexplained `repository` parameter, but the annotations and description together give an agent enough to call the tool correctly.

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 must carry parameter meaning. It does explain that `system` is a name from project_memory, but it does not explain the `repository` parameter at all, leaving one of two required parameters without added semantics.

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 clearly identifies the resource: everything remembered about one system in a project. It enumerates the kinds of information returned, such as past failures, fixes, changed files, authors, and dependencies, though it does not explicitly distinguish this tool from sibling tools like similar_past_failures.

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?

The description implies usage for retrieving a system's history and notes that `system` must come from project_memory, which is a useful prerequisite. However, it does not explicitly state when to use this tool versus alternatives or when not to use it.

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