Skip to main content
Glama

Who is in a city

people_in_place
Read-onlyIdempotent

Members or businesses in one city (or country) on the Knowasiak map, with what they do and what they are here for. On a signed-in connection, people the member follows or who follow them come first.

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": {
      "place": "<place>"
    },
    "name": "people_in_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoPeople (members) or businesses. Default: people.
limitNoHow many. Default: 20.
placeYesA city ("Mumbai", "Austin, US"), a country name, or a place_id from people_map.
offsetNoSkip this many (next page).
here_forNoOnly members here for this.
industryNoOnly this industry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description does add one genuinely useful trait annotations cannot express: results are ranked by social proximity on a signed-in connection. It says nothing about return shape or how paging behaves at the limit boundary.

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 resource and scope, then the ranking caveat. No filler or repetition of schema facts. It could be marginally tighter, but every clause carries information.

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?

With six parameters, three enums, no output schema, and several close siblings, the description covers the core semantics but leaves out result shape and alternative-tool selection. The ranking note is a strong addition; the missing routing guidance is the notable gap.

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 every parameter is already documented, including defaults, enum values, and the 40-item cap. The description's 'what they do and what they are here for' loosely maps to the industry and here_for filters but adds no syntax, format, or constraint detail beyond the schema. Baseline 3 is appropriate.

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 names the resource precisely ('Members or businesses in one city (or country) on the Knowasiak map') and adds what each entry carries ('what they do and what they are here for'), which lets an agent distinguish this from a bare directory lookup. It stops short of contrasting itself with discover_people or people_map, so sibling differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this rather than discover_people, find_businesses, or people_map — the nearest alternatives. The only routing hint ('place_id from people_map') lives in the schema, not the description, so an agent scanning descriptions gets no guidance on choosing between tools.

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