headlo-mcp

Official

by headlohq

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

get_context

Fetch all sites and workspaces for the active agency to establish context and orient yourself before proceeding.

Instructions

Get all sites and workspaces for the active agency — call this first to orient yourself

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_context"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Aug 6, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It correctly implies a read-only operation ('Get') scoped to the active agency, but does not disclose response format, whether it includes nested details, or any potential edge cases (e.g., no sites/workspaces). This is adequate but not rich.

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?

The description is a single sentence, front-loaded with the core action, and contains no redundant or filler information. Every word earns its place, making it highly concise and well-structured.

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 zero-parameter getter with no output schema, the description sufficiently conveys the tool's role as an orientation entry point. It mentions the key resources (sites and workspaces) and the operational context (active agency). Slightly more detail about the return structure could improve it, but the simplicity and usage cue make it adequate.

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?

The tool has zero parameters, so schema coverage is 100% by definition. Per the rubric, the baseline for 0 params is 4. The description adds no parameter semantics, but none are needed.

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 clearly states the tool retrieves all sites and workspaces for the active agency, using a specific verb ('Get') and resource. This distinguishes it from sibling tools that focus on individual modules, records, or pages, making the purpose unmistakable.

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?

The instruction 'call this first to orient yourself' explicitly tells the agent when to use the tool (before others) and why (orientation). It does not list alternative tools or exclusions, but the temporal guidance provides strong context for selection.

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