Skip to main content
Glama

Find a place to travel to

find_place
Read-onlyIdempotent

Finds a place in Sydney a buyer travels to, such as a hospital, university or station, with the position find_homes takes in profile.commute. Answers from Sagashi's own list of places.

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": {
      "text": "<text>"
    },
    "name": "find_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesWhat the buyer called it: at least a couple of letters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behaviour. The description adds real context beyond them: results come from 'Sagashi's own list of places', meaning a finite curated dataset rather than open geocoding, and the returned position is formatted for profile.commute. It does not say what happens on no match or ambiguity, which is the main remaining gap.

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

Conciseness4/5

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

Two sentences, front-loaded with the core verb and resource before the commute-integration detail. The phrasing 'with the position find_homes takes in profile.commute' is slightly convoluted and requires prior knowledge of the profile structure, but no sentence is filler.

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 lookup with full schema coverage and annotations covering safety, the description supplies the two things the structured fields cannot: the closed dataset source and how the result plugs into profile.commute, which substitutes for the absent output schema. Only no-match/ambiguity behaviour is left unaddressed.

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% and the single parameter already documents itself as 'What the buyer called it: at least a couple of letters'. The description adds only indirect meaning via the place-type examples (hospital, university, station), which hints at the kind of string expected. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

States a specific verb and resource ('finds a place in Sydney a buyer travels to') and scopes it with concrete examples (hospital, university, station). It also clarifies the output's role, matching the position find_homes takes in profile.commute, which lets an agent distinguish it from find_school or find_suburb. No explicit sibling routing is stated, so it stops short of a 5.

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 through the commute framing: this is the lookup to run when populating profile.commute. There is no explicit when-not-to-use or named alternative (e.g. find_school for schools, find_suburb for suburbs), which is especially relevant given the overlapping concept of a 'university' place. Adequate context, but the agent must infer the boundaries.

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