Skip to main content
Glama

Vivere

by dev.vivere
OverviewDiscussionsAdmin

Check in

check_in

Report on a heartbeat monitor: 'success' after a completed run (resets the deadline), 'start' when a run begins, 'fail' when it failed. Include a short message; it is kept as the run log.

Input Schema

NameRequiredDescriptionDefault
itemsNoOptional: how many items the run handled (tickets, rows, emails)
modelNoOptional: the model the run used, e.g. claude-sonnet-4-5
statusNoDefault success
messageNoOptional summary or error text to store with the run
cost_usdNoOptional: what the run cost in US dollars, e.g. 0.042
monitor_idYesMonitor id (the last path segment of the ping URL)
input_tokensNoOptional: input tokens the run used
output_tokensNoOptional: output tokens the run used
cache_read_tokensNoOptional: cache read input tokens
cache_write_tokensNoOptional: cache creation input tokens

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / cache_read_tokens
      Added value: +{
+  "description": "Optional: cache read input tokens",
+  "type": "integer"
+}
    • addedInput schema / properties / cache_write_tokens
      Added value: +{
+  "description": "Optional: cache creation input tokens",
+  "type": "integer"
+}
    • addedInput schema / properties / cost_usd
      Added value: +{
+  "description": "Optional: what the run cost in US dollars, e.g. 0.042",
+  "type": "number"
+}
    • addedInput schema / properties / input_tokens
      Added value: +{
+  "description": "Optional: input tokens the run used",
+  "type": "integer"
+}
    • addedInput schema / properties / items
      Added value: +{
+  "description": "Optional: how many items the run handled (tickets, rows, emails)",
+  "type": "integer"
+}
    • addedInput schema / properties / model
      Added value: +{
+  "description": "Optional: the model the run used, e.g. claude-sonnet-4-5",
+  "type": "string"
+}
    • addedInput schema / properties / output_tokens
      Added value: +{
+  "description": "Optional: output tokens the run used",
+  "type": "integer"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, non-idempotent), so the description adds the more valuable behavioral facts: a 'success' call resets the deadline, and the message is persisted as the run log. It omits auth/permission requirements and failure behavior (e.g., pinging a paused monitor), keeping it below a 5.

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?

Two tight sentences: the status semantics are front-loaded and the log-storage note follows immediately. No filler, no restating of the name or title.

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 10-parameter tool where the schema already documents every field, the description covers the core call semantics well. It does not address what happens on error/invalid status or what the call returns (no output schema exists), leaving a small gap.

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?

Schema coverage is 100%, so the baseline is 3. The description earns above baseline by explaining status semantics that the schema only lists as enum values, notably that 'success' resets the monitor deadline and that message is stored as the run log.

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 gives a specific verb+resource: reporting run status to a heartbeat monitor. It is clearly distinct from siblings like pause_monitor/resume_monitor, but it never names or contrasts those siblings, so it stops short of full differentiation.

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?

It gives concrete when-to-use guidance per status: 'success' after a completed run, 'start' when a run begins, 'fail' when it failed. There is no when-not guidance or explicit alternative tool mentioned, so it is clear context without exclusions.

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

All Vivere toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources