Skip to main content
Glama

Discover people to follow

discover_people
Read-onlyIdempotent

Knowasiak's Discover: people and businesses worth following, each with why they were picked, plus who follows whom among them. With no arguments on a signed-in connection, the member's own suggestions. Give similar_to (a username) for "Show similar": people like that profile. Give followers_of or following_of for one account's network. Or search by words and filters.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many. Default: 20.
queryNoWords in their name, bio or posts, e.g. "packaging design" or "D2C founder".
countryNoTwo-letter country code. A Knowasiak Pro filter: used only when the connected member has Pro. For places, people_in_place works for everyone.
industryNoIndustry: software (Software & IT), ecommerce (E-commerce & retail), marketing (Marketing & advertising), consulting (Consulting & services), finance (Finance & fintech), health (Health & wellness), education (Education & training), real_estate (Real estate & construction), manufacturing (Manufacturing & industrial), food (Food & hospitality), travel (Travel & tourism), media (Media & entertainment), creative (Design & creative), logistics (Logistics & transport), energy (Energy & environment), legal (Legal services), nonprofit (Non-profit & community), home_services (Home & local services), beauty (Beauty & personal care), automotive (Automotive), sports (Sports, fitness & recreation), events (Events & weddings), pets (Pets & animals), export_import (Export & import), coaching (Coaching & tuition), textiles (Textiles & garments), agriculture (Agriculture & farming), interiors (Interior design & furniture).
verifiedNoOnly verified accounts.
team_sizeNoCompany size.
similar_toNoA username: people like this profile (Show similar).
has_websiteNoOnly accounts with a website.
followers_ofNoA username: the people who follow this account.
following_ofNoA username: the people this account follows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the bar is lower. The description still adds real context: the default relies on a signed-in connection, results carry 'why they were picked' explanations, and country is a Pro-only filter that silently does nothing for non-Pro members — an important behavioral caveat.

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?

Front-loaded purpose followed by one sentence per mode, with no filler. Phrasing is slightly telegraphic ('With no arguments on a signed-in connection, the member's own suggestions'), but every sentence carries information an agent needs.

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 10-parameter, zero-required tool with no output schema, the description covers the default path, each mode, and the Pro gating caveat, and it hints at return content. It does not mention how limit interacts with modes or pagination, a minor gap given full schema coverage.

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 per-parameter meaning is already documented and baseline would be 3. The description goes further by grouping parameters into mutually exclusive modes (similar_to vs followers_of vs following_of vs query+filters) and by warning that country only applies under Pro, which the schema alone states but does not frame as a conditional filter.

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?

States the resource concretely (people and businesses worth following, each with the reason they were picked, plus follow relationships) and the tools' modes. The 'Knowasiak's Discover' framing plus the explicit mode list makes the purpose distinguishable from a plain search tool.

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

Usage Guidelines5/5

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

Enumerates the invocation modes: no arguments yields the member's own suggestions, similar_to yields 'Show similar', followers_of/following_of yield a network, and query plus filters yields a text search. It also routes place-based lookups to people_in_place, an explicit alternative with a stated condition.

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