Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_snapshot_get_latest_push

Read-onlyIdempotent

Retrieves the current push status for a snapshot at a specific location using company-level credentials, so you can verify deployment state.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only for all snapshots ops. Get Last Snapshot Push Get Latest Snapshot Push Status for a location id Endpoint: GET /snapshots/snapshot-status/{snapshotId}/location/{locationId} (Version header: v3; source: v3/snapshots-v3.json) Requires an Agency (company-level) token.

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": {
      "companyId": "<companyId>",
      "snapshotId": "<snapshotId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_snapshot_get_latest_push"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYes
locationIdYes
snapshotIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds genuinely useful context beyond that: the agency/company-level token requirement (stated twice) plus the v3 version header and source spec, which directly affects whether a call can succeed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The auth requirement is correctly front-loaded, but it is then repeated in three separate places (leading banner, parenthetical note, trailing sentence), and 'Get Last Snapshot Push' merely restates the annotation title. Redundant rather than wasteful overall.

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

Completeness3/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 ideally would say what the status response contains or how 'no push' is reported. It covers auth, endpoint, and version, which are the essentials for calling it, but leaves the return shape and empty-state behavior unexplained.

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. The endpoint template documents snapshotId and locationId as path segments, which is real added semantics, but companyId is only indirectly gestured at via 'agency-level token', leaving one of three required params undocumented.

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 names a specific verb and resource ('Get Latest Snapshot Push Status for a location id') and pins it to an exact endpoint, so an agent can distinguish it from siblings like ghl_snapshot_get_pushes_between_dates. It does not explicitly contrast those siblings, which keeps it below a 5.

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 when-to-use is only implied by the endpoint shape: fetch the most recent push status for a given snapshot/location. There is no explicit guidance on when to prefer ghl_snapshot_get_pushes_between_dates versus this tool, and no mention of what happens when no push exists.

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

Deploy Server

Other Tools