google-maps-remote: server now serves 6 tools, entry lists 3

Open Beginner friendly
#1,914 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
go, json
Domain
devtools

Research direction

Read registries/toolhive/servers/google-maps-remote/server.json and find the entry for google-developer-knowledge-remote. Update both entries' tool lists to reflect the tools and descriptions reported in the issue. Done means both entries match the reported server tools; the issue does not name a test or validation command.

Written by the indexing model from the issue text.

Description

needs-triage

registries/toolhive/servers/google-maps-remote/server.json lists 3 tools for https://mapstools.googleapis.com/mcp: search_places, lookup_weather, compute_routes.

A tools/list read of that endpoint today (2026-11-07, unauthenticated, no tool called) returns 6:

  • compute_routes
  • lookup_weather
  • resolve_maps_urls
  • resolve_names
  • search_along_route
  • search_places

search_along_route appeared between our reads of 27 Oct and 6 Nov, and the same read showed rewritten descriptions for compute_routes and lookup_weather. On 6 Nov https://developerknowledge.googleapis.com/mcp (google-developer-knowledge-remote) also rewrote all 3 of its tool descriptions while keeping the same names.

Suggest refreshing both entries' tool lists.

(Disclosure: I work on CrawlCheck, which re-reads registry servers. The change history for both servers is public at https://crawlcheck.io/mcp/changes.)

Dominant language
Go
Stars
26
Forks
104
Avg merge
1d 4h
Merged PRs (30d)
69

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stacklok/toolhive-catalog

All issues in stacklok/toolhive-catalog

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.