Skip to main content
Glama

What AddressLore covers

coverage
Read-only

The Vancouver local areas, streets, blocks and directory years AddressLore covers: every directory year read with names (each area's extra years said), the years read for the whole city, the later years that hold buildings and places only, and the census years, with each local area's count of streets and addresses and its page. Ask again with area for that area's streets, each with its blocks, its own years and its page.

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

Input Schema

NameRequiredDescriptionDefault
areaNoA City of Vancouver local area as listed in areas ("Strathcona", or its slug "strathcona"): lists its streets.
pageNoWhich page, when an answer says it has more than one (pages, next_page); 1 if left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / area
      Added value: +{
      +  "description": "A City of Vancouver local area as listed in areas (\"Strathcona\", or its slug \"strathcona\"): lists its streets.",
      +  "type": "string"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Which page, when an answer says it has more than one (pages, next_page); 1 if left out.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already mark it read-only and closed-world. The description adds data-scope context about which years, areas, counts, and pages are included, but it does not discuss response shape, pagination behavior, or limits beyond the schema's page field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is a long, clause-heavy run-on that is hard to parse; the second adds the area drill-down, but the overall structure is not cleanly segmented or front-loaded. The content is relevant, but presentation could be substantially tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only coverage query with no output schema, the description enumerates the main categories of coverage and the area drill-down, which is adequate. It still leaves the exact response structure and pagination behavior to inference, so it is not fully complete.

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 coverage is 100%, so area and page are already documented in the input schema. The description adds that area returns streets with blocks, years, and a page, but it does not clarify the page parameter's semantics beyond what the schema already provides.

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 identifies the resource as AddressLore's coverage data for Vancouver local areas, streets, blocks, and directory years, and explains the area drill-down. It is clear enough to distinguish from find_house/house_history, but it lacks an explicit action verb and does not name alternatives.

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?

It gives an explicit follow-up path—call again with area to get that area's streets, blocks, years, and page—but never states when to use this coverage tool rather than find_house or house_history, nor any prerequisites. Usage is implied from the coverage framing rather than clearly guided.

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