Skip to main content
Glama

Daily check history

get_server_history
Read-onlyIdempotent

Use when the user asks whether a server has been answering lately: daily check results (reachable, response time) of one server for up to 30 days.

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": {
      "name": "<name>"
    },
    "name": "get_server_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
nameYesRegistry name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description usefully adds the data content (reachability, response time) and the 30-day window cap. It does not say what happens for an unknown server or with an empty history, so it adds context but not full behavioral depth.

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?

A single sentence with the usage trigger front-loaded and the payload described immediately after. Nothing extraneous.

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 two-parameter read tool with no output schema, the description covers the key return content (reachable, response time per day) and the time bound. Minor gaps remain around entry granularity and behavior for unknown or new servers.

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 50%: 'name' is documented as 'Registry name' in the schema, while 'days' has no schema description. The description partially compensates by saying 'up to 30 days' and 'daily', implying the windowing semantics, but never explains the default or the resolution/granularity of days. Baseline 3 for this coverage.

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?

States a specific verb+resource: it returns daily check results (reachable, response time) for one server. This is clearly not get_server (current state) or get_changes, but the description never names those siblings, so differentiation is inferred rather than stated.

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?

Gives an explicit trigger: 'Use when the user asks whether a server has been answering lately.' That is a clear context cue. It stops short of exclusions or pointing to alternatives like get_server for current status.

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