Skip to main content
Glama
Sign In

MyLegend — public profiles, rich cards and personal agents

by io.github.falsalama
OverviewDiscussionsAdmin

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

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

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely non-obvious behavior: a hard cap of 10 matches, inclusion of labelled fictional demos, and the caveat that a match is not independent verification. It does not mention pagination or latency, but for a read-only lookup this is well above the annotation baseline.

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 with the usage trigger, then result shape, then disambiguation, then the follow-up call. Dense but every clause carries a distinct instruction; the 'location is not a search field' line mildly duplicates the schema text, costing a point.

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?

With no output schema, the description still specifies the return shape (max 10 matches with job/organisation/location context, including labelled demos), the disambiguation policy, and the next-step tool call. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100% and the single query parameter is fully documented with examples and the location caveat, so the schema already carries the semantics. The description reinforces rather than extends it, making the baseline 3 correct.

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?

The description states a specific verb and resource ('locating a person's owner-published MyLegend profile') and enumerates the searchable fields (name, headline, job title, organisation), which cleanly separates it from get_profile, the sibling it routes to for the rich card.

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?

It gives explicit when-to-use triggers, an explicit exclusion ('Location is not a search field'), ambiguity handling ('ask for clarification if multiple plausible people remain'), and a named hand-off ('call get_profile once with the returned slug') when the user wants a card.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MyLegend — public profiles, rich cards and personal agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources