Skip to main content
Glama

Woodpecker: NYC HPD registration lookup

Woodpecker's yearly price by building size

get_woodpecker_price
Read-onlyIdempotent

The flat yearly price for a building with a given number of apartments, what the plan includes, and the renewal price. Buildings with more than 20 apartments are quoted by email.

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": {
      "apartments": "<apartments>"
    },
    "name": "get_woodpecker_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
apartmentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent, non-open-world operation. The description adds valuable behavioral context by specifying what is returned (yearly price, plan inclusions, renewal price) and the business limitation for buildings over 20 apartments.

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 definition uses two compact sentences with no wasted wording. The core price lookup is front-loaded, and the usage limitation follows immediately.

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 simple one-parameter lookup with no output schema, the description gives enough information about the return content and the over-20-apartment exception. Minor details such as currency or exact error behavior for large buildings are left unspecified, but the core context is present.

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?

Although the schema has 0% description coverage, the description compensates by explaining that the single required parameter is the number of apartments in the building. It also defines the important business boundary that buildings with more than 20 apartments require an email quote.

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?

The description states a specific resource and scope: the flat yearly price for a building with a given number of apartments, including plan inclusions and renewal price. It clearly distinguishes itself as a price lookup rather than an ordering or building-lookup tool, though it does not explicitly name any sibling alternative.

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 implies usage for obtaining a yearly price and notes the important exception that buildings with more than 20 apartments are quoted by email. However, it does not explicitly say when to use this tool instead of siblings such as start_woodpecker_order or lookup tools.

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.