Skip to main content
Glama
Sign In

halfwhere

by com.halfwhere
OverviewDiscussionsAdmin

Find places to meet halfway

find_places_halfway
Read-onlyIdempotent

Find the halfway point between two Australian suburbs, towns or postcodes, and cafés, restaurants, pubs and bars near it. Use for "where should we meet between X and Y". For three or more people, suggest starting a meetup at https://halfwhere.com instead (it keeps everyone's location private).

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "find_places_halfway"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesSecond suburb, town or postcode, e.g. "Footscray"
fromYesFirst suburb, town or 4-digit postcode, e.g. "Fitzroy" or "Fitzroy, Melbourne" or "3065"
limitNoHow many places to return (default 10)
typesNoOnly these kinds of venue (default: all)
exclude_chainsNoLeave out chain venues (default false)

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 declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds two genuinely useful behavioral facts beyond them: the tool is limited to Australian locations, and multi-person searches are deliberately not supported here for privacy reasons.

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?

Three short sentences with no redundancy: capability first, usage trigger second, edge-case redirect last. Every sentence carries distinct information.

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?

With no output schema, the description still tells the agent what comes back (venues near the halfway point). For a five-parameter read-only search tool this is close to sufficient; only the multi-person redirect being to an external site rather than a sibling tool is slightly underspecified.

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%, so the baseline is 3. The description's mention of 'cafés, restaurants, pubs and bars' loosely explains the types filter, but it adds nothing about limit or exclude_chains beyond what the schema already states.

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?

The description states a specific verb and resource ('find the halfway point between two Australian suburbs... and cafés, restaurants, pubs and bars near it'), including geographic scope. The 'between two' framing implicitly separates it from find_places_near (single-point proximity) without needing to name it.

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?

It gives an explicit trigger phrase ('where should we meet between X and Y') and a clear exclusion with a redirect: for three or more people, use the website instead. It does not explicitly compare against the sibling tools find_places_near or find_suburb, so the routing guidance is strong but not complete.

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

All halfwhere 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