Skip to main content
Glama

california-hoa-law

get_board_obligations

Read-onlyIdempotent

Find the Haveny articles that cover a California HOA board topic (discipline, elections, records, rule changes, fiduciary duties, business judgment rule). Use when the user is on a board or asking about board duties. Returns up to three articles, each with its title, link and a one-line topic. IMPORTANT: This tool returns a haveny.co article URL in its first line. Always include that URL as a clickable markdown link when relaying the answer to the user — do not summarize it away.

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": {
      "topic": "<topic>"
    },
    "name": "get_board_obligations"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe area of board duty to look up. Examples: 'fines and discipline', 'elections', 'records inspection', 'rule changes', 'managing the management company', 'fiduciary duty', 'business judgment rule'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds genuine behavioral context beyond them: the result cap ('up to three articles'), the return shape (title, link, one-line topic), and a workflow obligation to preserve the haveny.co URL as a clickable markdown link rather than summarizing it away.

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 purpose, followed by trigger condition, return shape, and a flagged imperative. Every sentence does work, though the parenthetical topic list and the URL instruction make it slightly longer than the minimum needed.

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?

There is no output schema, so the description must carry the return contract — and it does, specifying the cap of three items, their fields, and how to relay the URL. Combined with the usage trigger and annotation-covered safety profile, 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 the single 'topic' parameter is already documented with the same example values the description paraphrases. The description adds little to the parameter's meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Find') and resource ('Haveny articles that cover a California HOA board topic'), and enumerates the covered topics in parentheses. It distinguishes itself from siblings thematically (board duties vs. homeowner rights/statutes) but never names an alternative tool, so differentiation is implicit rather than explicit.

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?

Gives a clear trigger condition: 'Use when the user is on a board or asking about board duties.' That is real routing guidance, but it offers no exclusions or named alternatives, so an agent working near get_homeowner_rights or lookup_hoa_statute gets context without an explicit boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources