Skip to main content
Glama

Woodpecker: NYC HPD registration lookup

Link to pay for a building's plan

start_woodpecker_order
Read-onlyIdempotent

Returns the link where the owner of a given building sees the city's record and the price and pays by card. Nothing is created until the owner pays on that page.

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": {
      "hpd_building_id": "<hpd_building_id>"
    },
    "name": "start_woodpecker_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
hpd_building_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety floor is covered. The description adds genuinely useful behavioral context that the annotations do not: nothing is persisted until the owner actually pays on the returned page, which tells the agent the call itself is side-effect free but a later user action is not. It omits any mention of prerequisites (e.g. an existing plan) or link expiry.

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?

Two short sentences with zero filler, and the important behavioral caveat (nothing is created until payment) is placed immediately after the core action. Every clause earns its place.

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 one-parameter read-only tool with no output schema, the description covers what is returned (a link) and the key side-effect semantics, which is close to sufficient. What remains missing is minor: prerequisites for a valid call and any note about link lifetime or failure modes.

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?

With a single parameter and 0% schema description coverage, the description carries the burden and only partially does so: 'a given building' implies the parameter identifies a building but never explains what hpd_building_id is, its expected source, or how to obtain a valid value. The parameter name is fairly self-explanatory, which keeps this at a minimum-viable 3 rather than lower.

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 uses a specific verb ('Returns the link') tied to a concrete resource (the city record/price/payment page for a given building), which is clearly distinct from a price-lookup sibling. It stops short of naming which sibling to use when the agent only wants the price, so it is clear but not fully differentiated.

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?

Usage is implied by the mention of the owner paying by card, giving the agent a reasonable sense of when this applies. There is no explicit when-not guidance or pointer to get_woodpecker_price for the read-only price case, so alternatives must be inferred.

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.