Skip to main content
Glama

Sisoco One

Recent events for an entity

sisoco_recent_events
Read-onlyIdempotent

Recent events stored for one entity, newest first, each with its type, severity, official source and source URL; event types are those of the packs this key can use. Pass the entity id (ent_…) returned by a check or lookup. An empty list means no events were recorded in the window, not that nothing happened. Cost: 1 lookup from the monthly quota (same as GET /v1/entities/{entity_id}/events).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMost recent events to return (1–100)
entity_idYesEntity id (ent_…) as returned by check or a lookup
since_daysNoLook back this many days (1–365)

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the bar is lower. The description still adds quota cost (1 lookup, equivalent to the underlying GET endpoint) and event-type scoping by the packs the key can use, both of which the agent cannot see in annotations.

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?

Front-loaded with what the tool returns, then prerequisite, then the empty-result caveat and cost. Every clause carries information, though the single dense sentence chain makes it slightly harder to scan than a split structure would.

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

Completeness5/5

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

For a three-parameter read tool with a full output schema, the description covers the remaining agent-critical facts: how to obtain the id, the meaning of an empty result, event-type scoping, and the quota cost. Nothing needed to call it correctly is missing.

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%, so entity_id, limit and since_days are already documented with patterns, ranges and defaults. The description reinforces entity_id provenance and alludes to a lookback 'window' but adds no syntax or defaults beyond the schema, making 3 the appropriate baseline.

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 resource (recent events for one entity) with ordering (newest first) and returned fields (type, severity, official source, source URL). It also names the provenance of the entity id (returned by a check or lookup), which ties it to the sibling check tool without ambiguity.

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?

Explains the prerequisite (an ent_… id from a check or lookup) and gives explicit interpretation guidance: an empty list means nothing was recorded in the window, not that nothing happened. It stops short of naming a sibling alternative or an explicit when-not-to-use condition.

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