Skip to main content
Glama
Sign In

Woodpecker: NYC HPD registration lookup

by help.woodpecker
OverviewDiscussionsAdmin

Who must register with HPD and when

explain_hpd_filing_requirements
Read-onlyIdempotent

HPD's rules in plain words: who must file the yearly property registration, the May 21 to September 1 window, who files the December bed bug report, what happens without a valid registration, and who signs. Sourced from HPD's own pages.

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": "explain_hpd_filing_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the bar is lower. The description adds meaningful context beyond them: the content is plain-language prose sourced from HPD's own pages, telling the agent to expect summarized rules rather than structured records.

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?

A single sentence, front-loaded with the framing ('HPD's rules in plain words') followed by a compact enumeration of covered topics. Every clause maps to a distinct question the tool answers, with no filler.

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 explanatory tool with no output schema, the description covers the topic scope thoroughly enough for an agent to decide to call it. It could note that the response is narrative text and any caveats about currency of the rules, but little essential information is missing.

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 takes no parameters, so the baseline is 4. The description correctly implies a pure knowledge lookup with nothing to supply, and there are no argument semantics left undiscussed.

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?

Names the specific subject (HPD property registration rules) and enumerates the exact questions answered: who must file, the May 21–September 1 window, the December bed bug filing, consequences of no registration, and who signs. This plainly separates it from sibling tools that return violation or building data.

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 description makes clear this is an explanatory/rules reference rather than a data lookup, which implicitly tells an agent when to reach for it. It does not explicitly say when to prefer it over the data-returning siblings or note that it takes no arguments, leaving that to inference.

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

All Woodpecker: NYC HPD registration lookup toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources