Skip to main content
Glama
Sign In
ghl-api-mcp

ghl-api-mcp

by S5-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_section

Fetch a documentation section by title or partial title. Get targeted API details without loading the full documentation file.

Instructions

Retrieve a documentation section by title or partial title.

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": {
      "title": "<title>"
    },
    "name": "get_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesSection title, such as 'Search Object Records'.
max_charsNoMaximum number of section characters to return (default: 4000).
whitelabel_domainNoOptional whitelabel API domain or base URL to use when rendering endpoint URLs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided; description discloses key parameters but omits search behavior (e.g., case sensitivity, exact vs. partial match). Adequate but not thorough.

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?

Single sentence, no fluff. Front-loaded with purpose. Efficient.

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?

Lacks output description, but given simple retrieval and no output schema, it is minimally complete. Could mention return type or format.

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%; description adds no meaning beyond schema descriptions. Baseline score appropriate.

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?

Description uses specific verb 'Retrieve' and resource 'documentation section', clearly distinguishing from sibling tools like get_document (full document) and get_endpoint_details (endpoint-specific).

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?

No explicit when-to-use or alternatives, but the purpose is straightforward. Minimal guidance, acceptable for a simple retrieval tool.

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