Skip to main content
Glama

made.show

Search people

search_people
Read-only

Find people across every public portfolio on made.show by free text (name with or without accents, headline, bio, role titles, organizations, skills), skills, location or availability. Returns short summaries with one suggested follow-up prompt each; call get_profile or get_portfolio for depth.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many people to return, 1 to 25
queryNoFree text: a name, role, company, skill or anything in a bio, e.g. "design systems lead fintech" or "backend go payments"
skillsNoAll listed skills must be evidenced
locationNoCity or country
disciplineNoWhat they do: designers, developers (engineering), product managers or writers. Self-chosen, so also check their roles.
remoteOnlyNoOnly people open to remote work
availabilityNoopen: looking now. passive: open to the right offer. not_looking: not looking

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / discipline
      Added value: +{
      +  "description": "What they do: designers, developers (engineering), product managers or writers. Self-chosen, so also check their roles.",
      +  "enum": [
      +    "design",
      +    "engineering",
      +    "product",
      +    "writing"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Free text: a name, role, company, skill or anything in a bio, e.g. \"design systems lead fintech\""New value: +"Free text: a name, role, company, skill or anything in a bio, e.g. \"design systems lead fintech\" or \"backend go payments\""
  2. Changed4 schema fields changed
    • addedInput schema / properties / availability / description
      Added value: +"open: looking now. passive: open to the right offer. not_looking: not looking"
    • addedInput schema / properties / limit / description
      Added value: +"How many people to return, 1 to 25"
    • addedInput schema / properties / query / description
      Added value: +"Free text: a name, role, company, skill or anything in a bio, e.g. \"design systems lead fintech\""
    • addedInput schema / properties / remoteOnly / description
      Added value: +"Only people open to remote work"
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, and the description adds genuinely new context: results are short summaries rather than full records, each carries one suggested follow-up prompt, and the search surface is limited to public portfolios. It does not discuss ranking, relevance, or paging beyond the limit cap, which keeps it below a 5.

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

Conciseness5/5

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

Two sentences, no filler. Scope and matching surface come first, and the escalation path to the detail tools is placed last where an agent looks for next steps.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must characterize the return value, and it does: short summaries with one suggested follow-up prompt each. Combined with 100% schema coverage on seven optional parameters and annotations covering the safety profile, nothing essential for correct invocation is missing.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning beyond the schema by clarifying that free text matches names with or without accents, plus headline, bio, role titles, organizations and skills. It also frames the field families (skills, location, availability) at a glance, though `discipline`, `remoteOnly` and `limit` are left entirely to the schema.

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 a specific verb and resource ("Find people") plus the scope ("across every public portfolio on made.show") and enumerates the searchable dimensions: free text, skills, location, availability. It also names the depth-oriented siblings (get_profile, get_portfolio), so an agent can separate discovery from retrieval without opening a schema.

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

Usage Guidelines4/5

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

The closing clause "call get_profile or get_portfolio for depth" gives explicit routing to alternatives for the follow-up step. What is not covered is when to prefer the free-text `query` versus the structured `skills`/`location`/`discipline` filters, so an agent must infer the query strategy.

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