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

ghl-mcp-server-v2

by zackscriven

ghl_invoice_get_settings

Read-onlyIdempotent

Retrieve invoice settings for a specified location or agency to review configuration and billing preferences.

Instructions

Get Invoice Settings Get the invoice settings for the given location Endpoint: GET /invoices/settings (Version header: v3; source: v3/invoices-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: invoices.readonly

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": {
      "altId": "<altId>",
      "altType": "<altType>"
    },
    "name": "ghl_invoice_get_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id or Agency Id
altTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the Agency or Sub-Account token requirement, the invoices.readonly scope, and the concrete GET endpoint, which lets an agent reason about auth failures up front. Return payload shape is not described, but with a read-only annotation profile this is a solid disclosure.

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 the core action in the first two lines, then prerequisite facts in short labeled lines. The endpoint source path (v3/invoices-v3.json) is mild internal boilerplate that does not help an agent select or invoke, but it costs little.

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 simple two-parameter read with full annotation coverage, no output schema, and no nested objects, the description supplies everything needed: what it fetches, the scope identifier, auth requirements, and the underlying endpoint. Nothing required 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 50%: altId is documented as "Location Id or Agency Id" while altType has an enum with no explanation. The description reinforces location scope ("for the given location") but does not resolve why altType only accepts "location" while the description mentions Agency tokens, leaving a small ambiguity the agent must resolve by trial.

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 verb and resource ("Get the invoice settings") plus the scoping entity ("for the given location"), which is unambiguous against a large sibling list where no other tool retrieves invoice settings. An agent knows exactly what this returns conceptually without opening the schema.

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?

Usage context is only implied: the tool takes a location/agency id, so it is used to read the settings for that scope. The description adds no when-to-use vs when-not guidance and names no alternative, though the stated token requirement and OAuth scope do serve as invocation prerequisites.

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