Skip to main content
Glama

Where members are

people_map
Read-onlyIdempotent

The Knowasiak people map: the places with the most members or businesses, at city level (or a country, for members without a city), optionally only those in one industry or here for one reason, with how many each industry and reason has. Members appear at their city, never an exact position; members who hid themselves are not counted.

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

Input Schema

NameRequiredDescriptionDefault
typeNoPeople (members) or businesses. Default: people.
limitNoHow many places. Default: 20.
here_forNoOnly members here for this: learn (Here to learn), connect (Open to meeting people), share (Sharing what they build), market (Following their industry), customers (Looking for customers).
industryNoOnly this industry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds real context the annotations cannot: results are city-level only ('never an exact position'), hidden members are excluded, and members lacking a city roll up to a country bucket. That privacy and bucketing behavior is exactly what an agent needs before presenting numbers.

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?

A single front-loaded sentence that opens with the resource and then layers scope, fallback, filters, and the privacy caveat. It is dense but every clause carries information; only the slightly run-on semicolon structure costs it a point.

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 carries the return-value burden and does so: places, counts per place, and per-industry/per-reason tallies, plus the exclusion of hidden members. What remains unstated is shape (ordering, field names) and default values, though those live in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning beyond the schema: filtering by industry or reason still returns 'how many each industry and reason has', i.e. the filters scope the place set rather than suppressing the breakdown. That clarifies result semantics for three of the four parameters.

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?

Names a specific resource and operation: the 'people map' of places ranked by member/business concentration at city level, with country-level fallback. That is concrete enough to distinguish it from a listing tool, though it never names a sibling like people_in_place or discover_people to sharpen the boundary.

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 by the superlative framing ('places with the most members'), which tells the agent this is for top-place discovery rather than listing people. There is no explicit when-not guidance or pointer to the sibling tools that handle per-person or per-place lookups.

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