Skip to main content
Glama

Pethost

by dev.pethost
OverviewDiscussionsAdmin

Pethost

Show
Read-onlyIdempotent

Shows the person a live view of their Pethost in the conversation: the machine with every project, one project, a project's uptime (its checks, alerts and incidents), its HTTP requests (a chart and the top paths) or its logs, the last two with filters they can change themselves. Call it when they ask to see something, or when a view says more than a sentence would: a day's traffic, a log to read through. It returns no data: GetMachine, GetProject, QueryHttpTraffic and QueryContainerLogs do. Afterwards say in a line what they are looking at, not what it shows. Where their app shows no views, the answer has the panel's link to give them.

Input Schema

NameRequiredDescriptionDefault
viewNomachine: its CPU, memory and disk, and every project. project: one project's state, address, services and last deploy. uptime: a project's checks, alerts and incidents. requests: a project's HTTP requests. logs: a project's log lines. Absent = machine.
rangeNorequests and logs: how far back. Absent = 24h.
searchNologs: the lines that contain it. requests: the paths that contain it.
statusNorequests: one class of answers.
serviceNologs: one service's lines. Absent = every service's.
project_idNoFor every view but machine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / view / description
      Previous value: -"machine: its CPU, memory and disk, and every project. project: one project's state, address, services and last deploy. requests: a project's HTTP requests. logs: a project's log lines. Absent = machine."New value: +"machine: its CPU, memory and disk, and every project. project: one project's state, address, services and last deploy. uptime: a project's checks, alerts and incidents. requests: a project's HTTP requests. logs: a project's log lines. Absent = machine."
    • changedInput schema / properties / view / enum
      Previous value: -[
-  "machine",
-  "project",
-  "requests",
-  "logs"
-]New value: +[
+  "machine",
+  "project",
+  "uptime",
+  "requests",
+  "logs"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely non-obvious behavior: it renders a view in the conversation, returns no data, supports user-adjustable filters, and changes the required post-call narration. That is substantial context beyond the structured metadata.

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 core purpose is front-loaded and every sentence carries information, though the single dense paragraph is somewhat run-on and could be broken up for scanability.

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?

With no output schema, the description correctly explains that no data is returned and that a sibling should be used for data, and it covers the follow-up behavior expected of the agent. Nothing essential for correct invocation 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 description coverage is 100% and every parameter already carries a per-value description, so the schema does the heavy lifting. The prose restates the view modes and notes that filters apply to requests/logs, but adds little beyond the enum documentation.

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?

The description pairs a specific verb ("shows ... a live view") with a concrete resource and enumerates all five view modes (machine, project, uptime, requests, logs). It clearly distinguishes this rendering tool from the data-returning siblings GetMachine/GetProject/QueryHttpTraffic/QueryContainerLogs.

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

Usage Guidelines5/5

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

It states explicitly when to call it ("when they ask to see something, or when a view says more than a sentence would") and names the alternative tools that return data instead. The routing condition between this and the query tools is unambiguous.

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

All Pethost toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources