Skip to main content
Glama

MyLegend — public profiles, rich cards and personal agents

Find a public profile

find_person
Read-only

Use this when locating a person's owner-published MyLegend profile by name, headline, job title or organisation. Returns at most 10 matches with approved job, organisation and location context, including labelled fictional demos. Compare supplied context with those fields; ask for clarification if multiple plausible people remain. Location is not a search field. When the user requests a profile or rich card and the person is resolved, call get_profile once with the returned slug. A match is not independent verification.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesA name, headline, job title or organisation name from the published profile. Examples: Morgan Example or SR3H. Use location to compare returned matches, not as a search term.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"A name, headline, job title or organisation name from the published profile. Examples: Danny Griffin or SR3H. Use location to compare returned matches, not as a search term."New value: +"A name, headline, job title or organisation name from the published profile. Examples: Morgan Example or SR3H. Use location to compare returned matches, not as a search term."
    • changedInput schema / properties / query / examples
      Previous value: -[
      -  "Danny Griffin",
      -  "SR3H"
      -]New value: +[
      +  "Morgan Example",
      +  "SR3H"
      +]
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources